Date: Sun, 29 Oct 2006 15:08:26 +0000
From: Gavin Hamill <gdh@laterooms.com>
To: pgsql-performance@postgresql.org
Subject: Re: VACUUMs take twice as long across all nodes
Message-Id: <20061029150826.80afe324.gdh@laterooms.com>
In-Reply-To: <20061029145825.GB14585@phlogiston.dyndns.org>
References: <20061026095827.9e85e1c0.gdh@laterooms.com>
	<20196.1161874041@sss.pgh.pa.us>
	<20061026160609.5e94e581.gdh@laterooms.com>
	<20061026191728.GD26892@nasby.net>
	<20061026213556.174bd7b5.gdh@laterooms.com>
	<20061026220937.GA6866@phlogiston.dyndns.org>
	<20061027102025.8183c5d9.gdh@laterooms.com>
	<20061029145825.GB14585@phlogiston.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit


Hi :)

[pg_dump from a Slony replica]

> That's not the problem.  The problem is that when you restore the
> dump of the slave, you'll have garbage.  Slony fools with the
> catalogs on the replicas.  

>  (And you might as well throw away the
> dumpfiles from the replicas that you have.  They won't work when you
> restore them.)

This is interesting, but I don't understand.. We've done a full restore
from one of these pg_dump backups before now and it worked just great.

Sure I had to DROP SCHEMA _replication CASCADE to clear out all the
slony-specific triggers etc., but the new-master ran fine, as did
firing up new replication to the other nodes :)

Was I just lucky?

Cheers,
Gavin.