Re: large dumps won't restore
От | Christian Fowler |
---|---|
Тема | Re: large dumps won't restore |
Дата | |
Msg-id | Pine.LNX.4.61.0410201140250.26812@leda.steelsun.com обсуждение исходный текст |
Ответ на | Re: large dumps won't restore (Weiping <laser@qmail.zhengmai.net.cn>) |
Ответы |
Re: large dumps won't restore
|
Список | pgsql-admin |
Joshua - well, i ran a --inserts dump as you suggested, and it died upteen millions (and many hours) in at: INSERT 59235383 1 invalid command \033', cannot allocate memory for output buffer Weiping, db=# \encoding UNICODE the last four columns in the table are: full_name_nd | character varying(200) | mod_date | timestamp without time zone | pc_char | character varying(4) | dim_char | character varying(16) | [root@host root]# env |grep LANG LANG=en_US.UTF-8 On Wed, 20 Oct 2004, Weiping wrote: > Christian Fowler wrote: > >> >> I'm running a large database ( data dir is ~9gigs ) on Fedora Core 2 with >> 7.4.5-PGDG rpm's >> >> When using the -Fc dump method + pg_restore, I get: >> >> -bash-2.05b$ pg_restore -Fc -d foo -L backup.list >> /tmp/02\:43-postgresql_database-foo-backup >> pg_restore: ERROR: invalid input syntax for type timestamp: "52.233334" >> CONTEXT: COPY foo_data, line 42529, column mod_date: "52.233334" >> pg_restore: [archiver (db)] error returned by PQendcopy >> > what's the column type before the column "mod_date"? > is it's a text type? if so, then have you used any kind of encoding for your > database? > what's it? and what's your PGCLIENCODING setting? > > seems like a encoding problem I've ever met, but not sure. > > regards > > Laser > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > [ \ / [ >X< Christian Fowler | spider AT viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org
В списке pgsql-admin по дате отправления: