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 3F6C6D1B8CF for ; Thu, 28 Aug 2003 22:47:47 +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 17898-06 for ; Thu, 28 Aug 2003 19:47:17 -0300 (ADT) Received: from snoopy.oit.edu (snoopy.OIT.EDU [140.211.135.12]) by svr1.postgresql.org (Postfix) with ESMTP id 4EF56D1B8E7 for ; Thu, 28 Aug 2003 19:47:11 -0300 (ADT) Received: from fireserve.net (purvine-141-62.oit.edu [140.211.141.62]) by snoopy.oit.edu (8.12.9/8.12.9/OIT-4.0) with ESMTP id h7SMlCHf018390; Thu, 28 Aug 2003 15:47:12 -0700 Message-ID: <3F4E87A8.9010005@fireserve.net> Date: Thu, 28 Aug 2003 15:52:24 -0700 From: Dennis Gearon User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, ru, es-mx 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> <3F4E6D52.90206@Yahoo.com> <1062108258.29020.69.camel@haggis> In-Reply-To: <1062108258.29020.69.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/1657 X-Sequence-Number: 48072 Are these clusters physically together using dedicate LAN lines .... or are they synchronizing over the Interwait? Ron Johnson wrote: >On Thu, 2003-08-28 at 16:00, Jan Wieck wrote: > > >>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. >> >> > >I guess it's the differing protocols involved. DEC made clustering >(including Rdb/VMS) work over an 80Mbps protocol, back in The Day, >and HPaq says that it works fine now over fast ethernet. > > > >>>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? >> >> > >Not as sure as I am that the sun will rise in the east tomorrow, >but, yes, I am highly confident that O modified DLM for use in >9i RAC. Note that O purchased Rdb/VMS from DEC back in 1994, along >with the Engineers, so they have long knowledge of how it works >in VMS. One of the reasons they bought Rdb was to merge the tech- >nology into RDBMS. > > >