Re: Fixing up a corrupted toast table - Mailing list pgsql-general

From Tom Lane
Subject Re: Fixing up a corrupted toast table
Date
Msg-id 18863.1141859240@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fixing up a corrupted toast table  (Steve Atkins <steve@blighty.com>)
Responses Re: Fixing up a corrupted toast table  (Steve Atkins <steve@blighty.com>)
Re: Fixing up a corrupted toast table  ("Marko Kreen" <markokr@gmail.com>)
List pgsql-general
Steve Atkins <steve@blighty.com> writes:
>>> make it happy by inserting a dummy row into the toast table (chunk ID
>>> as specified in the error, chunk sequence 0, any old data value).

> Any attempt to touch the toast table gives me:
> ERROR:  cannot change TOAST relation "pg_toast_17410"

Ugh.  Maybe we should allow superusers to do that?  Or is it too much of
a foot-gun?

> If I set relkind to 'r' for the toast table, shove some fake data
> in there and set it back to 't' that should do it, shouldn't it?

Offhand I think this would work, but suggest trying it in a scratch
database first ...

            regards, tom lane

pgsql-general by date:

Previous
From: Steve Atkins
Date:
Subject: Re: Fixing up a corrupted toast table
Next
From: "Paul Newman"
Date:
Subject: Re: Triggers and Multiple Schemas.