recover as much as possible (xlog flush request not satisfied)

From: Wim Goedertier <Wim_Goedertier(at)symantec(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: recover as much as possible (xlog flush request not satisfied)
Date: 2012-07-08 10:59:29
Message-ID: 86F664E344B1E441B0ED88956B92759E6F0AE23DDF@EDO1XCHEVSPIN32.SYMC.SYMANTEC.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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?
I'm happy if I can recover 80 or 90% of the database.
Unfortunately, there are no dumps/backups available.

Can you give some pointers to extract as much data as possible out of the database?
How difficult would it be to extract data directly from the files containing the data?
(FYI: the fields used in the most important table are: bigint, character varying(32), character(1), integer, smallint, text)

Regards,
Wim Goedertier

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2012-07-08 16:06:21 Re: recover as much as possible (xlog flush request not satisfied)
Previous Message Tom Lane 2012-07-07 16:09:23 Re: BUG? Regular expression matching of optional character group at beginning of RE