| From: | CG <cgg007(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org, Adrian Klaver <aklaver(at)comcast(dot)net> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Subject: | Re: pg_dump and ON DELETE CASCADE problem |
| Date: | 2009-12-10 20:21:44 |
| Message-ID: | 108673.19429.qm@web37902.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks for the suggestion. I'm not sure what you mean when you say I should restore to a file. Do you mean I should dump the database to an SQL file instead of the "compressed" format?
What do you think I will find?
In the database dump, it is including a row that should be marked as deleted. I can select on that key in the production database and get zero rows, and I can select on that key in the restored database and find the row. When I ignore errors the data is restored, but the foreign key can't be created (and that is the only error I encounter). The presence of the data in the dump can not be contested... :)
--- On Thu, 12/10/09, Adrian Klaver <aklaver(at)comcast(dot)net> wrote:
>
> One thing that comes to mind is to restore the dump file to
> a file instead of a
> database and see what is being dumped from the live
> database.
>
>
>
> --
> Adrian Klaver
> aklaver(at)comcast(dot)net
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2009-12-10 20:29:33 | Re: pg_dump and ON DELETE CASCADE problem |
| Previous Message | Scott Marlowe | 2009-12-10 18:19:49 | Re: ERROR: could not open relation with OID 59132 |