From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Steve Atkins" <steve(at)blighty(dot)com>, "pgsql general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Fixing up a corrupted toast table |
Date: | 2006-03-09 13:48:54 |
Message-ID: | e51f66da0603090548i929980bx7efbfcefc60165de@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/9/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Steve Atkins <steve(at)blighty(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2006-03-09 14:22:17 | Re: Perspective: PostgreSQL usage boon after release of 8.2 |
Previous Message | Tomi NA | 2006-03-09 13:14:20 | Re: database/schema level triggers? |