From: | Mikael Kjellström <mikael(dot)kjellstrom(at)mksoft(dot)nu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Corrupt view in PostgreSQL 9.0.9 |
Date: | 2012-09-28 17:31:58 |
Message-ID: | 5065DF0E.3050004@mksoft.nu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2012-09-28 19:26, Tom Lane wrote:
> =?ISO-8859-1?Q?Mikael_Kjellstr=F6m?= <mikael(dot)kjellstrom(at)mksoft(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-09-28 17:39:38 | Re: Corrupt view in PostgreSQL 9.0.9 |
Previous Message | Tom Lane | 2012-09-28 17:26:55 | Re: Corrupt view in PostgreSQL 9.0.9 |