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: Wed, 04 Mar 2009 22:13:50 +0000
Message-ID: <1236204830.31880.122.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <7123.1236202022@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>
On Wed, 2009-03-04 at 16:27 -0500, Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
> > On Wed, 2009-03-04 at 15:37 -0500, Tom Lane wrote:
> >> It's not as easy as all that. What will you do with updates to shared
> >> catalogs?
>
> > Apply them.
>
> ... which leaves your other databases in inconsistent states.
Which is not a problem if you didn't want to restore them in the first
place. You might complain that we would need safeguards to protect
people from trying to access non-restored databases and then failing to
understand why they aren't there.
--
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: <1236204830.31880.122.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