I have a (large) corrupted 8.3.7 database that I'd like to fix.
It has this problem :
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: missing chunk number 2 for toast
value 122220114 in pg_toast_16426
I've seen this particular syndrome before and fixed it by deleting the table
row that refers
to the missing toast value. The table row was discovered by chance because the user to whom the
data belonged complained that his service wasn't working. In this current case that hasn't
happened, so I'm clueless as to which row I need to delete.
I've tried dumping the table to see if the records happen to be in primary key
order
(hence the N+1'th record would be the bad one). Unfortunately this didn't help
because the records appear to be out of order in the dump.
Hence my question : is there an efficient way to determine which table row
references that missing toad value ?
My best option right now is to issue SELECT ... LIMIT .. OFFSET ... queries
to identify the row. This is likely to take a while though because there's
tens of GBytes in the table, and the database is quite heavily loaded.
Any better ideas are most welcome, thanks.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
