Re: PostgreSQL Active-Active Clustering

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL Active-Active Clustering
Date: 2024-07-16 02:26:26
Message-ID: CANzqJaA-Z3p1Bsv2EP=GCswEJG7Xjvu_ZZjuGMh=sh=_fkPO6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jul 15, 2024 at 5:54 PM Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>
wrote:

> ## Ron Johnson (ronljohnsonjr(at)gmail(dot)com):
>
> > This "lack of products" puzzles me, because DEC was doing this with VAX
> > (then Alpha and Itanium) clusters 40 years ago via a Distributed Lock
> > Manager integrated deep into VMS. Their Rdb and (CODASYL) DBMS products
>
> Tech and trade-offs have changed over the last 40 years :)
> These days you can so many cores in one package, while "more than one
> processor" was quite a feat in the 80ies ("A dual processor VAX 11/780",
> 1982 https://dl.acm.org/doi/10.5555/800048.801738; also the 11/782 and
> 11/784), and you get so much RAM and storage (even fast storage, if
> you keep it local) with that package. Response Latency really jumps
> if you have to communicate with anything outside your box.
> While latency matters, the number of problems where you absolutely
> need that distributed lock manager has not really grown that much,
> I think.

Customers still want High Availability, and VMS Clusters were great for
HA.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sud 2024-07-16 04:26:16 Re: Dropping column from big table
Previous Message Peter J. Holzer 2024-07-16 00:37:31 Re: Dropping column from big table