Subject: Re: Postgressql backup/restore question
From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>,
	samana srikanth <samanasrikanth@gmail.com>, pgsql-admin@postgresql.org
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>
Content-Type: text/plain
Date: Wed, 04 Mar 2009 22:13:50 +0000
Message-Id: <1236204830.31880.122.camel@ebony.2ndQuadrant>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


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