Thread: pg_dump problem

On Wed, 2007-11-14 at 10:32 -0800, SHARMILA JOTHIRAJAH wrote:
> Hi
> I try to use pg_dump to dump my database.
> pg_dump smrs
> and it gives me an error
> pg_dump: failed sanity check, parent table OID 670739 of pg_rewrite
> entry OID 670741 not found
>

check out the --oids option in the manuals ("man pg_dump")... could
help ?!

and try this:

pg_dump --oids smrs

Cheers
jmf

> What causes this problem?
> Thanks
> sharmila
>
>
>
>
> ______________________________________________________________________
> Be a better sports nut! Let your teams follow you with Yahoo Mobile.
> Try it now.

SHARMILA JOTHIRAJAH <sharmi_jo@yahoo.com> writes:
> pg_dump: failed sanity check, parent table OID 670739 of pg_rewrite entry OID 670741 not found

> What causes this problem?

Corrupt system tables, looks like :-(  What PG version is this?

I would suggest checking to see if either of those OIDs appears in
either the objid or refobjid columns of pg_depend.  If not, the
most likely theory is that this pg_rewrite entry somehow didn't
get deleted when its parent table was dropped.  You could just
delete it manually, eg,
    delete from pg_rewrite where oid = 670741;

If you do find other traces of the table it might be better to try
to resurrect the table (actually it's most likely a view not a
table).

            regards, tom lane

SHARMILA JOTHIRAJAH <sharmi_jo@yahoo.com> writes:
> looks like the OIDs are there....

Yeah, that makes it look more like the pg_class row went missing
than that there was an intentional drop of the view.

Does "VACUUM VERBOSE pg_class" report anything interesting?
It's possible also that reindexing pg_class would fix it.

            regards, tom lane

On Wed, Nov 14, 2007 at 10:32:54AM -0800, SHARMILA JOTHIRAJAH wrote:
> Hi
> I try to use pg_dump to dump my database.
> pg_dump smrs
> and it gives me an error
> pg_dump: failed sanity check, parent table OID 670739 of pg_rewrite entry OID 670741 not found

Is there any possibility you have Slony installed?  Is this a replica?  If
so, it's a well-known problem.  You can't use pg_dump under those
circumstances.

A

--
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke