Re: unable to dump database, toast errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lonni J Friedman <lfriedman(at)vasoftware(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: unable to dump database, toast errors
Date: 2003-04-03 21:32:53
Message-ID: 13725.1049405573@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Lonni J Friedman <lfriedman(at)vasoftware(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Lonni J Friedman 2003-04-03 21:38:50 Re: unable to dump database, toast errors
Previous Message Jason Hihn 2003-04-03 21:31:19 Re: Single Byte values