X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id EE5EF9DC840 for ; Wed, 1 Mar 2006 13:51:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 48464-04 for ; Wed, 1 Mar 2006 13:51:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from outbound.internet-mail-service.net (outbound6.internet-mail-service.net [216.240.47.197]) by postgresql.org (Postfix) with ESMTP id CD8B89DC80A for ; Wed, 1 Mar 2006 13:51:54 -0400 (AST) Received: from idiom.com (idiom.com [216.240.32.1]) by outbound.internet-mail-service.net (Postfix) with ESMTP id 5ECFB2417EF for ; Wed, 1 Mar 2006 09:51:54 -0800 (PST) Received: from [192.168.1.109] (adsl-69-107-112-198.dsl.pltn13.pacbell.net [69.107.112.198]) by idiom.com (8.12.11/8.12.11) with ESMTP id k21HpsAT098544 for ; Wed, 1 Mar 2006 09:51:54 -0800 (PST) (envelope-from bryce1@obviously.com) Message-ID: <4405DF32.4070307@obviously.com> Date: Wed, 01 Mar 2006 09:51:46 -0800 From: Bryce Nesbitt User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: pgsql-sql@postgresql.org Subject: Replication - state of the art? References: <20060301133041.8EFFA19B797@smtp03l.fasthosts.co.uk> In-Reply-To: <20060301133041.8EFFA19B797@smtp03l.fasthosts.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.241 required=5 tests=[AWL=0.052, MISSING_HEADERS=0.189] X-Spam-Score: 0.241 X-Spam-Level: X-Archive-Number: 200603/14 X-Sequence-Number: 24360 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