Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Now that I think about it, maybe my problem is not related to TOAST at
> all, but to a corrupted varlena field.
Right.
> So if the corruption does not
> involve toasting, I'm in the same position as before, i.e. I haven't
> found out what is the corrup
On Tue, Jun 07, 2005 at 05:48:31PM -0400, Tom Lane wrote:
> Comments? Anyone else ever wished they had this?
Hmm. There's another problem which shows up when the server throws an
error about an invalid allocation request. This also happens when a
varlena field is corrupted, but you don't have
I was just helping out some Red Hat colleagues who were trying to deal
with a corrupted database in which pg_dump was failing like so:
pg_dump: Error message from server: ERROR: missing chunk number 3 for toast
value 205026
Frequently the best recovery action for this involves finding and
delet
