On 2012-09-28 19:26, Tom Lane wrote:
=?ISO-8859-1?Q?Mikael_Kjellstr=F6m?= <mikael.kjellst...@mksoft.nu> writes:
I tried the reindex and then the manual delete of the view from
pg_class. That took care of the rows in pg_attribute but when I tried
to run pg_dump I now get this:
pg_dump: failed sanity check, parent table OID 16547 of pg_rewrite entry
OID 16550 not found
Oh, okay, pg_dump is doing more cross-checking than I remembered.
That's the ON SELECT rule for the broken view. You'll need to delete it
manually too, and perhaps also the pg_type row if pg_dump chances to
notice that. I doubt you'll need to clean up the pg_attribute rows.
Ok, that did the trick. Now the backup completed.
Your recomendation is to restore the backup to a new database and drop
the old one, right?
/Mikael
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
