You are right. There are no rows in pg_class with oids 670739 and 670741. Is that the problem? How do I fix that. Will deleting those rows from pg_depend fix this problem?
Also I have another question. Should the pg tables (like pg_class etc) generally be vacuumed regularly?
Thanks
sharmila
----- Original Message ----
From: Tom Lane <tgl@xxxxxxxxxxxxx>
To: SHARMILA JOTHIRAJAH <sharmi_jo@xxxxxxxxx>
Cc: pgsql-general@xxxxxxxxxxxxxx
Sent: Wednesday, November 14, 2007 3:33:20 PM
Subject: Re: pg_dump problem
SHARMILA JOTHIRAJAH <sharmi_jo@xxxxxxxxx> 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
From: Tom Lane <tgl@xxxxxxxxxxxxx>
To: SHARMILA JOTHIRAJAH <sharmi_jo@xxxxxxxxx>
Cc: pgsql-general@xxxxxxxxxxxxxx
Sent: Wednesday, November 14, 2007 3:33:20 PM
Subject: Re: pg_dump problem
SHARMILA JOTHIRAJAH <sharmi_jo@xxxxxxxxx> 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
Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.
