From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: samana srikanth <samanasrikanth@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgressql backup/restore question
Date: Thu, 05 Mar 2009 09:11:39 +0000
Message-ID: <1236244299.31880.135.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <8151.1236205187@sss.pgh.pa.us>
References: <e42828680903040356o307031c2k7898562d8e2d275c@mail.gmail.com>
<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>
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
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: simon@2ndQuadrant.com, tgl@sss.pgh.pa.us, peter_e@gmx.net, samanasrikanth@gmail.com
Subject: Re: Postgressql backup/restore question
In-Reply-To: <1236244299.31880.135.camel@ebony.2ndQuadrant>
* 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