Re: unable to dump database, toast errors - Mailing list pgsql-general

From Tom Lane
Subject Re: unable to dump database, toast errors
Date
Msg-id 13725.1049405573@sss.pgh.pa.us
Whole thread Raw
In response to Re: unable to dump database, toast errors  (Lonni J Friedman <lfriedman@vasoftware.com>)
Responses Re: unable to dump database, toast errors  (Lonni J Friedman <lfriedman@vasoftware.com>)
List pgsql-general
Lonni J Friedman <lfriedman@vasoftware.com> writes:
> ok, i've got 786 rows to play with, joy.  once i find a broken row/field,
> how do I map that back to pg_toast_302323?

Well, it'll tell you which chunk_id it's having a problem with; you
could then look into the toast table to see what the available data is.
(Although the odds are good that the data will have been compressed, so
you won't be able to tell much :-()

As far as recovering, just set the broken field to a new value.
Fortunately the old-value-deletion code is not picky about whether it
finds all the chunks that should be there.

            regards, tom lane


pgsql-general by date:

Previous
From: Jason Hihn
Date:
Subject: Re: Single Byte values
Next
From: Lonni J Friedman
Date:
Subject: Re: unable to dump database, toast errors