Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 11FC79FB875 for ; Tue, 19 Jun 2007 18:23:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 59192-01 for ; Tue, 19 Jun 2007 18:23:08 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from serv01.siteground137.com (ns1.siteground137.com [67.15.250.10]) by postgresql.org (Postfix) with ESMTP id 115A29FBE1F for ; Tue, 19 Jun 2007 18:22:59 -0300 (ADT) Received: from nat.vinton.com ([209.162.219.253]:51881 helo=dogma.v10.wvs) by serv01.siteground137.com with esmtpa (Exim 4.52) id 1I0l9z-000583-JV; Tue, 19 Jun 2007 16:22:48 -0500 Subject: Re: Replication From: Jeff Davis To: Craig James Cc: pgsql-performance@postgresql.org In-Reply-To: <4671CBBA.6010104@emolecules.com> References: <4671CBBA.6010104@emolecules.com> Content-Type: text/plain Date: Tue, 19 Jun 2007 14:22:49 -0700 Message-Id: <1182288169.1926.15.camel@dogma.v10.wvs> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - serv01.siteground137.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - j-davis.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.134 tagged_above=0 required=5 tests=AWL=-0.722, BAYES_50=0.001, FORGED_RCVD_HELO=0.135, SARE_SPEC_REPLICA=0.72 X-Spam-Level: X-Archive-Number: 200706/389 X-Sequence-Number: 25422 On Thu, 2007-06-14 at 16:14 -0700, Craig James wrote: > Looking for replication solutions, I find: > > Slony-I > Seems good, single master only, master is a single point of failure, > no good failover system for electing a new master or having a failed > master rejoin the cluster. Slave databases are mostly for safety or > for parallelizing queries for performance. Suffers from O(N^2) > communications (N = cluster size). > There's MOVE SET which transfers the origin (master) from one node to another without losing any committed transactions. There's also FAILOVER, which can set a new origin even if the old origin is completely gone, however you will lose the transactions that haven't been replicated yet. To have a new node join the cluster, you SUBSCRIBE SET, and you can MOVE SET to it later if you want that to be the master. Regards, Jeff Davis