Re: pg_rawdump

From: "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
To: Roberto Mello <roberto(dot)mello(at)gmail(dot)com>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_rawdump
Date: 2010-10-20 08:44:28
Message-ID: 20101020084428.GD15684@cuci.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Roberto Mello wrote:
>On Tue, Oct 19, 2010 at 6:13 PM, Stephen R. van den Berg <srb(at)cuci(dot)nl> wrote:
>> Greg Stark wrote:
>>>premise this on the idea that you've lost everything in the catalog
>>>but not the data in other tables. Which seems like a narrow use case.

>> It happens, more often than you'd think. ??My client had it, I've
>> seen numerous google hits which show the same.

>It happened to us recently when a customer had disk issues, and we

It usually happens when there are disk issues, that's exactly what it is for.

>A tool like Stephen is proposing would most likely have helped us
>recover at least some or most of the data, I would hope.

Well, because the customer could recreate (within reason) the original
table definitions, we were able to recover all of his data (12 tables,
including some toasted/compressed).

It's just that matching table and file, and subsequently figuring out
some missing columns which may have been added/removed later,
can be rather timeconsuming and could be made a lot easier (not necessarily
perfect) if that information would have been present in the first page of
a file.
--
Stephen.

Life is that brief interlude between nothingness and eternity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2010-10-20 10:12:49 Re: ISN patch that applies cleanly with git apply
Previous Message Stephen R. van den Berg 2010-10-20 07:13:45 Re: pg_rawdump