Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 8D0109FA250 for ; Fri, 5 Jan 2007 11:50:01 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 43708-05 for ; Fri, 5 Jan 2007 11:49:46 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A52EA9FA311 for ; Fri, 5 Jan 2007 11:49:52 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l05FnoBo016102; Fri, 5 Jan 2007 10:49:50 -0500 (EST) To: "Andy Shellam (Mailing Lists)" cc: pgsql-admin@postgresql.org Subject: Re: Recovering a deleted database problem 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> Comments: In-reply-to "Andy Shellam (Mailing Lists)" message dated "Fri, 05 Jan 2007 15:26:28 +0000" Date: Fri, 05 Jan 2007 10:49:50 -0500 Message-ID: <16101.1168012190@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/38 X-Sequence-Number: 24194 "Andy Shellam (Mailing Lists)" 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