| From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
|---|---|
| To: | Dick Kniep <dick(dot)kniep(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-02 12:35:29 |
| Message-ID: | 8615C29D-4421-43D6-AA48-32A4483BBCA5@solfertje.student.utwente.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2 Jan 2011, at 13:19, Dick Kniep wrote:
> 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.
I suppose you did already try restoring that dump and applying the log files to it and that failed?
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4d20711d11541020214904!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2011-01-02 13:04:10 | Finding recursive dependencies |
| Previous Message | Dick Kniep | 2011-01-02 12:19:20 | Re: Shit happens |