Re: pg_rawdump

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

On Tue, Oct 19, 2010 at 6:13 PM, Stephen R. van den Berg <srb(at)cuci(dot)nl> wrote:
> Greg Stark wrote:
>
>> But I'm not sure how useful. I mean, you can't really decipher
>>everything properly without the data in the catalog -- and you have to
>>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
were able to get the table files back through forensics, but the
control files were not in good shape, and the cluster wouldn't start.

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

Roberto

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-10-20 00:34:30 Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP)
Previous Message Greg Stark 2010-10-19 23:47:18 Re: Creation of temporary tables on read-only standby servers