Hi
Thanks
PG version is 8.2.3
I queried the pg_depend using this query
select * from pg_depend where objid in (670739,670741) or refobjid in
(670739,670741)
looks like the OIDs are there....
classid objid objsubid refclassid refobjid refobjsubid
deptype
---------- -------- ----------- ------------- ----------- --------------
----------
1247 670740 0 1259 670739 0
i
1259 670739 0 2615 2200 0
n
2618 670741 0 1259 670739 0
i
2618 670741 0 1259 670645 3
n
2618 670741 0 1259 670648 3
n
2618 670741 0 1259 670739 0
n
so what else can cause tis problem?
sharmila
----- Original Message ----
From: Tom Lane <[EMAIL PROTECTED]>
To: SHARMILA JOTHIRAJAH <[EMAIL PROTECTED]>
Cc: pgsql-general@postgresql.org
Sent: Wednesday, November 14, 2007 2:21:03 PM
Subject: Re: [GENERAL] pg_dump problem
SHARMILA JOTHIRAJAH <[EMAIL PROTECTED]> 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
____________________________________________________________________________________
Be a better pen pal.
Text or chat with friends inside Yahoo! Mail. See how.
http://overview.mail.yahoo.com/
