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 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
