pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Drew Whittle <drew@albatross.co.nz>
Cc: pgsql-admin@postgresql.org
Subject: Re: corrupt DB recovery
Date: Thu, 12 Aug 2004 00:21:58 -0400
Message-ID: <24307.1092284518@sss.pgh.pa.us> (raw)
In-Reply-To: <1092280216.25843.28.camel@mcp>
References: <1092280216.25843.28.camel@mcp>

Drew Whittle <drew@albatross.co.nz> writes:
> I have two other db's that are 100% identical in everything but name and
> data. (ie same structure etc), is it possible to use one of that data
> files in them to over write the buggered file and fix the pg_proc error?

You could try that, but unless the db's also have identical history (in
the sense of the same set of transaction numbers that committed) it's
unlikely to work.  I think your problem is not that pg_class is buggered
per se, so much as that you did not have correct pg_clog data to match it.
The data files and the log files are an interlocking whole, you can't
just plug in one part at random.

> Any other suggestions that might get the data back or should I just
> forget it and tell them to key it again?

If you did extract something from this mess, how much could you trust
it?  Not a lot, because the bad-clog problem will affect visibility of
rows in the user tables too.

I'm afraid you're screwed :-(.  Maybe you could learn something about
proper backup procedures though.  The backup you have obviously didn't
work well --- how did you take it exactly?

			regards, tom lane



view thread (3+ messages)  latest in thread

Message-ID: <24307.1092284518@sss.pgh.pa.us>
Permalink:  ../24307.1092284518@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24307.1092284518@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, drew@albatross.co.nz
  Subject: Re: corrupt DB recovery
  In-Reply-To: <24307.1092284518@sss.pgh.pa.us>
  References: <1092280216.25843.28.camel@mcp> <24307.1092284518@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox