Wim Goedertier <Wim_Goedertier@xxxxxxxxxxxx> writes: > I have a postgres db version 8.2.15 (Yes, I know it's rather old version). > After correcting some disk and file system problems the postgres table seems to be corrupt, returning: > ERROR: xlog flush request B67/44479CB8 is not satisfied --- flushed only to B67/429EB150 > CONTEXT: writing block 33652 of relation 1663/18776/21757 > on a simple select statement. > What is the best way to get past this? Well, *first*, stop the database and take a filesystem-level backup of the $PGDATA directory tree. That will at least let you get back to where you are now if experimentation makes it worse. You could suppress this particular class of complaints by using pg_resetxlog to advance the WAL endpoint past whatever's in the database. That won't do anything to fix corruption, it'll just silence this particular consistency check. But it might be enough to let you run pg_dump. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
