Konrad Garus wrote: > We use PG 8.3. We use pg_dump and pg_restore overnight to create > copies of main database for reporting etc. One dump/restore runs at 9 > PM, another at 11 PM. > > Today I discovered that the restore at 11 PM failed to recreate a > foreign key constraint, because one row from master table was missing. > It is also missing from main database, but not from the 9 PM dump. > > The main database is in curious state: The row from master table is > missing, the row referencing it from slave table is present, and > finally the FK constraint on slave is in place. > > Do you have any ideas on how it could possibly happen? What research > could help find the root cause and fix the database?
If that's really the case, it sounds like curruption. Is there anything in the server logs? Yours, Laurenz Albe -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
