Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4B6469FA33C for ; Fri, 5 Jan 2007 14:44:13 -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 95552-09 for ; Fri, 5 Jan 2007 14:44:01 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from perth.mailnetwork.co.uk (perth.mailnetwork.co.uk [80.175.28.46]) by postgresql.org (Postfix) with ESMTP id 3E17B9FA182 for ; Fri, 5 Jan 2007 14:44:02 -0400 (AST) Received: from user-514c037d.l1.c5.dsl.pol.co.uk ([81.76.3.125]:3821 helo=[192.168.1.2]) by perth.mailnetwork.co.uk with esmtpa (Exim 4.63) (envelope-from ) id 1H2u2t-0004Cv-9w; Fri, 05 Jan 2007 18:44:03 +0000 Message-ID: <459E9CAA.5090800@mailnetwork.co.uk> Date: Fri, 05 Jan 2007 18:44:58 +0000 From: "Andy Shellam (Mailing Lists)" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Tom Lane CC: pgsql-admin@postgresql.org Subject: Re: Recovering a deleted database problem References: <459E32DC.3030402@mailnetwork.co.uk> <15671.1168009739@sss.pgh.pa.us> <459E6E24.2090505@mailnetwork.co.uk> <16101.1168012190@sss.pgh.pa.us> In-Reply-To: <16101.1168012190@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/41 X-Sequence-Number: 24197 > 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. > It gets backed up at 2am in the morning and AFAIK there'd be very few (if any) transactions going through until about 5am, so it should be OK. > 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. > OK thanks for that Tom, after glancing through the online documentation, I've enabled logging of checkpoints etc. by setting "log_min_messages" to "log" - is this enough to log the times that transactions are committed, so I can find this info should I need it again in the future? Thanks, -- Andy Shellam NetServe Support Team the Mail Network "an alternative in a standardised world"