Replication - state of the art? - Mailing list pgsql-sql

From Bryce Nesbitt
Subject Replication - state of the art?
Date
Msg-id 4405DF32.4070307@obviously.com
Whole thread Raw
In response to Help with trigger that updates a row prior to a potentially aborted deletion?  ("Simon Kinsella" <simon@bluefiresystems.co.uk>)
Responses Re: Replication - state of the art?
Re: Replication - state of the art?
List pgsql-sql
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


pgsql-sql by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: grant select,... over schema
Next
From: Andrew Sullivan
Date:
Subject: Re: Help with trigger that updates a row prior to a potentially aborted deletion?