"Reid Thompson" <Reid.Thompson@xxxxxxxx> writes: > $ pg_dump -f table_dump.sql -t table_with_error dbname > FATAL 2: read of clog file 1559, offset 0 failed: Success You've got a clobbered tuple header in that file (ridiculous xmin or xmax value). Alternatively, given the evident age of this server, it could be a clobbered page header leading to the system following a bogus pointer to a tuple header. I think the track you want to pursue is identifying which page contains the bad data and looking at it with pg_filedump to see if there's anything recoverable there at all. If not, just zeroing out the page is probably the easiest way of getting to a dumpable state. You've probably lost this particular tuple in any case, you might or might not have lost the whole page. Once you get out of this, you might want to think about updating to something newer than 7.2 ... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
