From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | cgg007(at)yahoo(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org, Adrian Klaver <aklaver(at)comcast(dot)net>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Subject: | Re: pg_dump and ON DELETE CASCADE problem |
Date: | 2009-12-11 18:17:04 |
Message-ID: | dcc563d10912111017r122aad0ap67b194ace4713760@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Dec 10, 2009 at 1:21 PM, 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?
>
> 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... :)
This could be a corrupted index problem maybe? If you do this:
set enable_indexscan=off;
select * from table where key=value;
does it still not show up?
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2009-12-11 18:49:47 | Re: Postgres.exe Process taking too much memory and CPU usage - making the system extremely slow. |
Previous Message | John R Pierce | 2009-12-11 17:21:56 | Re: PostgreSQL installation under Win XP embeded |