pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andy Shellam (Mailing Lists) <andy.shellam-lists@mailnetwork.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: Recovering a deleted database problem
Date: Fri, 05 Jan 2007 10:49:50 -0500
Message-ID: <16101.1168012190@sss.pgh.pa.us> (raw)
In-Reply-To: <459E6E24.2090505@mailnetwork.co.uk>
References: <459E32DC.3030402@mailnetwork.co.uk>
	<15671.1168009739@sss.pgh.pa.us>
	<459E6E24.2090505@mailnetwork.co.uk>

"Andy Shellam (Mailing Lists)" <andy.shellam-lists@mailnetwork.co.uk> writes:
> Is it enough to simply have re-copied in the base/xxx directory from the 
> base backup, after the PITR recovery had completed (obviously any 
> changes made to that database since the base backup won't have been 
> restored but thankfully it's backed up nightly and doesn't change too 
> often :-) )

Well, I'd be a little worried about whether the base backup was
self-consistent, but if it was taken at a time where the DB was idle
then you can probably get away with this.

> What I'll probably do is try to simulate the same process again on a 
> different machine to get myself a bit more familiar.  Is there any other 
> situations you can think of where this may also be relevant, or is it 
> just when dropping a complete database?

AFAIK the only operations that have non-rollbackable side effects are
CREATE/DROP DATABASE and CREATE/DROP TABLESPACE.  For any of these,
you'd end up with inconsistent state if you try to stop replay just
before the commit record.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <16101.1168012190@sss.pgh.pa.us>
Permalink:  ../16101.1168012190@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/16101.1168012190@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, andy.shellam-lists@mailnetwork.co.uk
  Subject: Re: Recovering a deleted database problem
  In-Reply-To: <16101.1168012190@sss.pgh.pa.us>
  References: <459E32DC.3030402@mailnetwork.co.uk> <15671.1168009739@sss.pgh.pa.us> <459E6E24.2090505@mailnetwork.co.uk> <16101.1168012190@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