From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
---|---|
To: | cgg007(at)yahoo(dot)com |
Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump and ON DELETE CASCADE problem |
Date: | 2009-12-10 21:34:52 |
Message-ID: | 72108297.223251260480892212.JavaMail.root@sz0030a.emeryville.ca.mail.comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
----- "CG" <cgg007(at)yahoo(dot)com> wrote:
> 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?
See Johns answer.
>
> 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... :)
>
Well I often find what I 'know' and what is are not the same:) Basically restoring to the file replicates the database restore, with out the error hopefully. Looking at the data restored in the file might give you a clue to what is going on. Just one step in the process of resolving the problem.
Adrian Klaver
aklaver(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Glen Barber | 2009-12-10 22:46:12 | Restore time differences between full database dumps and separate schema/data dumps |
Previous Message | Eric B. Ridge | 2009-12-10 21:11:42 | Postgres "locked up" |