Re: [BUGS] Restoring 7.4.2 pg_dumpall output in 8.1.4 fails

On Thu, Aug 10, 2006 at 11:44:31AM -0700, Jie Liang wrote: > Tom, > I used: > pg_dumpall > db.out on my 7.4.2 server It's not a bug. Use the pg_dumpall from 8.1.4 to talk to the still-live 7.4.2 server :) Cheers, D -- David Fetter <[EMAIL PROTECTED]> http://fetter.org/ phone: +1 415 235 3778

Re: [BUGS] Restoring 7.4 "pg_dumpall -o" output in 8.1 fails

> ls -l total 282 -rwxr-xr-x 1 jliang wheel 210873 Aug 10 10:54 pg_dump -rwxr-xr-x 1 jliang wheel 57452 Aug 10 10:54 pg_dumpall These are pg_dump(all) executable from postgresql-8.1.4 I copied them onto my postgresql-7.4.2 server and chmod to executable. ---([EMAIL PROTECTED])--(11:05:06AM)-

[BUGS] Restoring 7.4.2 pg_dumpall output in 8.1.4 fails

Tom, I used: pg_dumpall > db.out on my 7.4.2 server Then, I use: psql -f db.out postgres on my 8.1.4 server. I got chunk of: 1232133 invalid command \N 1232134 invalid command \N I found that come from my inheritant table, the pg_dump(all) didn't make right order on parent and child tables, it dum

Re: [BUGS] BUG #2558: initDB failed to run

It was discussed but never committed to the CVS (as much as I know).   Subject: RE: [BUGS] BUG #2558: initDB failed to runDate: Wed, 9 Aug 2006 13:25:38 -0500From: [EMAIL PROTECTED]To: [EMAIL PROTECTED]CC: pgsql-bugs@postgresql.org Please cc the list so others can learn.   Yes, I think a pat