Date: Tue, 27 Jun 2006 14:37:39 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Fwd: Start up question about triggers
Message-ID: <20060627183739.GM27997@phlogiston.dyndns.org>
References: <20060627113936.GA27997@phlogiston.dyndns.org>
	<200606271148.k5RBmcQV027906@auth-smtp.hol.gr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200606271148.k5RBmcQV027906@auth-smtp.hol.gr>
User-Agent: Mutt/1.5.9i

On Tue, Jun 27, 2006 at 02:48:38PM +0300, Forums @ Existanze wrote:
> Hello again andrew,
> 
> Actually man I do need to be able to write to both databases, and keep them
> synchronized, and all this because of the recurring xenofobia for technology

Then sorry, but this can't be done out of the box by anything.  You
have all manner of race conditions here. 

> and the fear of "hackers" (I know the difference between hackers and

Moreover, this won't solve their problem: if someone compromised the
application, both databases would be corrupted.  There's no way to
avoid that in such a design.

Better to use Slony in log-shipping mode (or PITR) and keep backups
of all the change sets.  Then if someone broke in, you'd at least be
able to roll back to the known-good state.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
The fact that technology doesn't work is no bar to success in the marketplace.
		--Philip Greenspun