Date: Tue, 31 Jul 2007 09:36:19 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Database synchronization
Message-ID: <20070731133619.GB8583@phlogiston.dyndns.org>
References: <20070724143737.GA25948@apartia.fr>
	<004e01c7cea4$58046570$080d3050$@com>
	<46A724CB.3030405@archonet.com>
	<000001c7cea8$39775d20$ac661760$@com>
	<46A7449A.4080500@archonet.com>
	<001e01c7cf40$85e7b540$91b71fc0$@com>
	<6c3fb5eb0707310102s73bf7516w8dd157c550e2cf7d@mail.gmail.com>
	<46AEF12C.2090107@archonet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46AEF12C.2090107@archonet.com>
User-Agent: Mutt/1.5.9i

On Tue, Jul 31, 2007 at 09:22:04AM +0100, Richard Huxton wrote:
> I don't think slony lets you rename tables/schemas during transfer. I'm 
> not sure many people want it, and it would be a complicated thing to do 
> properly in the general case (you'll need to consider dependant objects 
> - FKeys, views, functions etc).

It doesn't allow this, but you could cause it to happen anyway on the
replica using a trigger.  You have to use STORE TRIGGER to make this
work.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
The whole tendency of modern prose is away from concreteness.
		--George Orwell