Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 88C216345F6 for ; Thu, 5 Mar 2009 05:07:58 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 05305-02 for ; Thu, 5 Mar 2009 05:07:46 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail128148.authsmtp.net (outmail128148.authsmtp.net [62.13.128.148]) by mail.postgresql.org (Postfix) with ESMTP id 399E9634266 for ; Thu, 5 Mar 2009 05:07:45 -0400 (AST) Received: from mail-c189.authsmtp.com (mail-c189.authsmtp.com [62.13.128.71]) by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n2597da4080106; Thu, 5 Mar 2009 09:07:39 GMT Received: from [192.168.0.3] (85-211-101-172.dyn.gotadsl.co.uk [85.211.101.172]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n2597cQh003671; Thu, 5 Mar 2009 09:07:39 GMT Subject: Re: Postgressql backup/restore question From: Simon Riggs To: Tom Lane Cc: Peter Eisentraut , samana srikanth , pgsql-admin@postgresql.org In-Reply-To: <8151.1236205187@sss.pgh.pa.us> References: <49AE8958.3070909@gmx.net> <1236198515.31880.108.camel@ebony.2ndQuadrant> <6347.1236199034@sss.pgh.pa.us> <1236200757.31880.116.camel@ebony.2ndQuadrant> <7123.1236202022@sss.pgh.pa.us> <1236204830.31880.122.camel@ebony.2ndQuadrant> <8151.1236205187@sss.pgh.pa.us> Content-Type: text/plain Date: Thu, 05 Mar 2009 09:11:39 +0000 Message-Id: <1236244299.31880.135.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 139b5537-0965-11de-bc7b-001f29070be2 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksachtFaABbYFhD HGQLW11EUFR7WWR/ aAMfZQBDYEtPQQRq UVZIRVBNFgBqBAMB SEAcVxB1JGQeeH5z Y0FjEHFcWEw0dEV0 EEtRFmobZW5mbX0e URQNalEHd1FXfh9E PFJ2VHQNMzAFKBg1 TUcAFhwUHBNqYBxS WR0CN18JWl8PVjQ1 TBMfBXI1EFYZQD8+ ZwU7J0UAHUEXWicA X-Authentic-SMTP: 61633235383639.kestrel.dmpriest.net.uk:1378/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/73 X-Sequence-Number: 31573 On Wed, 2009-03-04 at 17:19 -0500, Tom Lane wrote: > This behavior might be all right for an emergency recovery kind of tool, > but I can't see us considering it a supported feature. I agree post-recovery cleanup would be required to bring up a fully safe read-write database. That's one of the reasons my longer term thoughts are towards running transactions immediately after recovery completes, for other uses also. > The larger point though is that I suspect what the OP really is looking > for is "restore just this one database into my existing cluster, without > breaking the other databases that are already in it". There is zero > chance of ever doing that with a WAL-based backup --- transaction ID > inconsistencies would break it, even without considering the contents > of shared catalogs. Agreed. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support