Re: Corrupted Table

"Bryan White" <bryan@arcamax.com> writes:
> As a result of this event, in the log file I see:
> ---------------
> Server process (pid 21764) exited with status 139 at Mon Jul 31 14:51:44

Status 139 indicates a SEGV trap on most Unixen.  There should be a core
dump left by the crashed backend --- can you get a backtrace from it
with gdb?

I concur that this probably indicates corrupted data in the file.  We
may or may not be able to guess how it got corrupted, but a stack trace
seems like the place to start.

			regards, tom lane