pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dennis Gearon <gearond@fireserve.net>
To: Ron Johnson <ron.l.johnson@cox.net>
Cc: PgSQL General ML <pgsql-general@postgresql.org>
Subject: Re: Replication Ideas
Date: Thu, 28 Aug 2003 15:52:24 -0700
Message-ID: <3F4E87A8.9010005@fireserve.net> (raw)
In-Reply-To: <1062108258.29020.69.camel@haggis>
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>

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.
>
>  
>




view thread (22+ messages)  latest in thread

Message-ID: <3F4E87A8.9010005@fireserve.net>
Permalink:  ../3F4E87A8.9010005@fireserve.net/
Also on:    postgresql.org/message-id/3F4E87A8.9010005@fireserve.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: gearond@fireserve.net, ron.l.johnson@cox.net, pgsql-general@postgresql.org
  Subject: Re: Replication Ideas
  In-Reply-To: <3F4E87A8.9010005@fireserve.net>
  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> <3F4E87A8.9010005@fireserve.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox