From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | David Guimaraes <skysbsb(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Forensic recovery deleted pgdump custom format file |
Date: | 2015-07-14 03:00:57 |
Message-ID: | CAB7nPqT0qG2kBCNnYOA0B4p2j7DH50LpBM7NFTb=DtJr2hDf5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 14, 2015 at 11:20 AM, David Guimaraes <skysbsb(at)gmail(dot)com> wrote:
> Yeah bingo
Hm. While there is a magic-code header for the custom format, by
looking at the code I am not seeing any traces of a similar thing at
the end of the dump file (_CloseArchive in pg_backup_custom.c), and I
don't recall wither that there is an estimation of the size of the
dump either in the header. If those files were stored close to each
other, one idea may be to look for the next header present. or to
attempt to roughly estimate the size that they would have I am afraid.
In any case, applying reverse engineering methods seems like the most
reliable method to reconstitute an archive handler that could be used
by pg_restore or pg_dump, but perhaps others have other ideas.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2015-07-14 05:07:08 | Re: PostgreSQL 9.5 Alpha 1 build fail with perl 5.22 |
Previous Message | David Guimaraes | 2015-07-14 02:20:33 | Re: Forensic recovery deleted pgdump custom format file |