Re: pg_dump and ON DELETE CASCADE problem
От | Scott Marlowe |
---|---|
Тема | Re: pg_dump and ON DELETE CASCADE problem |
Дата | |
Msg-id | dcc563d10912111017r122aad0ap67b194ace4713760@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_dump and ON DELETE CASCADE problem (CG <cgg007@yahoo.com>) |
Ответы |
Re: pg_dump and ON DELETE CASCADE problem
|
Список | pgsql-general |
On Thu, Dec 10, 2009 at 1:21 PM, CG <cgg007@yahoo.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 dumpthe 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 productiondatabase and get zero rows, and I can select on that key in the restored database and find the row. When I ignoreerrors the data is restored, but the foreign key can't be created (and that is the only error I encounter). The presenceof 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?
В списке pgsql-general по дате отправления: