From: Bryce Nesbitt <bryce1@obviously.com>
Cc: pgsql-sql@postgresql.org
Subject: Replication - state of the art?
Date: Wed, 01 Mar 2006 09:51:46 -0800
Message-ID: <4405DF32.4070307@obviously.com> (raw)
In-Reply-To: <20060301133041.8EFFA19B797@smtp03l.fasthosts.co.uk>
References: <20060301133041.8EFFA19B797@smtp03l.fasthosts.co.uk>
I'm interested in creating a mirror database, for use in case one our
primary machine goes down. Can people here help sort out which of the
several replication projects is most viable?
As far as I can tell, the winner is slony1 at
http://gborg.postgresql.org/project/slony1/projdisplay.php , but there
are several contenders.
------------------------------------------
The needs here are very relaxed. We have one main postmaster which runs
24x7x365. There's another machine nearby that can accept a log or
journal of some sort. The alternate never needs DB access, except in
case of main machine failure, and then we can take up to 15 minutes to
switch over and rebuild the DB. "No-lost transaction" is far more
important than switch time.
Anyone here using replication or transaction journaling? Has it proved
reliable, easy to maintain?
Bryce Nesbitt
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-sql@postgresql.org
Cc: bryce1@obviously.com
Subject: Re: Replication - state of the art?
In-Reply-To: <4405DF32.4070307@obviously.com>
* 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