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

From Marko Kreen
Subject Re: Fixing up a corrupted toast table
Date
Msg-id e51f66da0603090548i929980bx7efbfcefc60165de@mail.gmail.com
Whole thread Raw
In response to Re: Fixing up a corrupted toast table  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 3/9/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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?

+1 on allowing superusers to do that.  I recently needed it.

Especially cool would be if i could simply insert untoasted
values there, so i can put some fake values there and detect them
later.  (As I cannot query 'what table row has toast_oid')

--
marko

pgsql-general by date:

Previous
From: "Tomi NA"
Date:
Subject: Re: database/schema level triggers?
Next
From: "Merlin Moncure"
Date:
Subject: Re: Perspective: PostgreSQL usage boon after release of 8.2