| From: | "Jie Liang" <jliang(at)stbernard(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Restoring 7.4.2 pg_dumpall output in 8.1.4 fails |
| Date: | 2006-08-10 18:44:31 |
| Message-ID: | 5E5A4BA7825B8742BB58DDF3B7041BF92BFF23@mail01.stbernard.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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 dumped child tables first
then parent table, so I restore them, it try to create child table first
which will fail definitely then all the data try to be loaded later on
will be errored out. I am not sure 8.1.4's pg_dump(all) fixed this bug
or not. Currently, I think I can work around it by editing the order on
archive.list file and use pg_restore.
Best Regards,
Jie Liang
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-08-11 01:31:24 | Re: Restoring 7.4.2 pg_dumpall output in 8.1.4 fails |
| Previous Message | Jie Liang | 2006-08-10 18:25:27 | Re: Restoring 7.4 "pg_dumpall -o" output in 8.1 fails |