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 09CCCD1D7FA for ; Thu, 28 Aug 2003 21:15:03 +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 05300-03 for ; Thu, 28 Aug 2003 18:14:33 -0300 (ADT) Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by svr1.postgresql.org (Postfix) with SMTP id 6C888D1D923 for ; Thu, 28 Aug 2003 18:01:37 -0300 (ADT) Received: from pcp01341166pcs.wilog301.pa.comcast.net (HELO europa.janwieck.net) (janwieck@68.80.245.191 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 28 Aug 2003 21:01:37 -0000 Received: from Yahoo.com (ismtp.afilias.com [216.217.55.254]) (authenticated) by europa.janwieck.net (8.11.6/8.11.6) with ESMTP id h7SL1Kx05756; Thu, 28 Aug 2003 17:01:20 -0400 Message-ID: <3F4E6D52.90206@Yahoo.com> Date: Thu, 28 Aug 2003 17:00:02 -0400 From: Jan Wieck User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ron Johnson Cc: PgSQL General ML Subject: Re: Replication Ideas References: <200308270325.h7R3PfI24921@candle.pha.pa.us> <6358.1061955430@sss.pgh.pa.us> <1061971951.18060.357.camel@haggis> In-Reply-To: <1061971951.18060.357.camel@haggis> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/1640 X-Sequence-Number: 48055 Ron Johnson wrote: > Notes: > a) this is, of course, not *sufficient* for multi-master > b) yes, you need a fast, low latency network for the DLM chatter. "Fast" is an understatement. The DLM you're talking about would (in our case) need to use Spread's AGREED_MESS or SAFE_MESS service type, meaning guarantee of total order. A transaction that needs any type of lock sends that request into the DLM group and then waits. The incoming stream of lock messages determines success or failure. With the overhead of these service types I don't think one single communication group for all database backends in the whole cluster guaranteeing total order will be that efficient. > > This is a tried and true method of synchronization. DEC Rdb/VMS > has been using it for 19 years as the underpinnings of it's cluster > technology, and Oracle licensed it from them (well, really Compaq) > for it's 9i RAC. Are you sure they're using it that way? Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #