From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Dick Kniep <dick(at)lindix(dot)nl> |
Cc: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Shit happens |
Date: | 2011-01-03 19:46:40 |
Message-ID: | 1294084000.1748.13.camel@jdavis-ux.asterdata.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, 2011-01-02 at 10:31 +0100, Dick Kniep wrote:
> Hi list,
>
> Thanks for the clear answer. However, this is the simple answer that
> is also in the manual. Yes I know it is not directly possible to get
> that data, but I am quite desparate to get the data back. If one way
> or another the data is (except for the 4 days we really have no data
> for) accessible, we will write a program to recover the data into the
> production database. So if anyone of you knows about a way to access
> the actual data in the WAL file (or a reference where to find enough
> information to do this) I would be very happy.
>
The WAL segment files will contain a lot of information (including some
full page images), which may be enough to recover some of your data.
Obviously, you'll be missing most of the data from that 4-day period,
but there is some hope.
However, pulling that data out of the WAL and making sense out of it
will be tricky, indeed (as Radosław already mentioned).
Email lists are probably not the best way to make it through this kind
of tricky recovery. You might consider contacting one of the PostgreSQL
consulting companies:
http://www.postgresql.org/support/professional_support
where someone experienced with WAL recovery can help you personally.
Some of these organizations employ people who have done extensive
development on the WAL recovery system and know it _very_ well.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Vincent Veyron | 2011-01-03 20:21:30 | Re: problem updating from form |
Previous Message | Jasen Betts | 2011-01-03 18:52:17 | Re: Merging 2 rows in a table |