X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id B8F9FD1B8BC for ; Thu, 28 Aug 2003 07:06:33 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 69376-10 for ; Thu, 28 Aug 2003 04:06:03 -0300 (ADT) Received: from smtp.pspl.co.in (unknown [202.54.11.65]) by svr1.postgresql.org (Postfix) with ESMTP id 0E94CD1B8B3 for ; Thu, 28 Aug 2003 04:05:58 -0300 (ADT) Received: (from root@localhost) by smtp.pspl.co.in (8.12.9/8.12.9) id h7S7APuN029954 for ; Thu, 28 Aug 2003 12:40:25 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) (authenticated bits=0) by persistent.co.in (8.12.9/8.12.9) with ESMTP id h7S7AOhi029941 for ; Thu, 28 Aug 2003 12:40:24 +0530 From: "Shridhar Daithankar" To: pgsql-general@postgresql.org Date: Thu, 28 Aug 2003 12:37:53 +0530 MIME-Version: 1.0 Subject: Re: Replication Ideas Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3F4DF7A1.21007.3477A6E@localhost> In-reply-to: <20030826025754.V691@ganymede.hub.org> References: <11627.1061845759@sss.pgh.pa.us> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/1569 X-Sequence-Number: 47985 On 26 Aug 2003 at 3:01, Marc G. Fournier wrote: > > > On Mon, 25 Aug 2003, Tom Lane wrote: > > > Chris Travers writes: > > > Yes I have. Postgres-r is not a high-availability solution which is > > > capable of transparent failover, > > > > What makes you say that? My understanding is it's supposed to survive > > loss of individual servers. > > How does it play 'catch up' went a server comes back online? PITR + archive logs daemon? Chances of a node and an archive log daemon going down simalrenously are pretty low. If archive log daemon works on another machin, the MTBF should be pretty acceptable.. Bye Shridhar -- The Briggs-Chase Law of Program Development: To determine how long it will take to write and debug a program, take your best estimate, multiply that by two, add one, and convert to the next higher units.