Michael Guerin <guerin@rentec.com> writes:
> Tom Lane wrote:
>>> "Dumping and reloading the table that owns this toast table would be a safer route; it would at
>>> least make it real clear what damage you'd suffered."
> I tried using pg_dump and copy, but both get errors and fail. Is there
> another way that I should try to export the data?
That's about what I expected would happen. What you're now down to is
having to identify and delete the specific rows that suffered damage.
Once you can do a "SELECT *" from the table without error, pg_dump will
work.
> Also, I sent another post recently trying to find out how these things
> happen. The drives seem to be ok, although I still need to memcheck.
> This is the second corruption in a 4 day span, but I can't find any
> clues to why its happening.
I'd be pretty suspicious about bad RAM if I were you ...
regards, tom lane
