Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sTXts-00HObf-SM for pgsql-general@arkaria.postgresql.org; Tue, 16 Jul 2024 02:26:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sTXtp-00Erkh-Mf for pgsql-general@arkaria.postgresql.org; Tue, 16 Jul 2024 02:26:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sTXtp-00ErkZ-AA for pgsql-general@lists.postgresql.org; Tue, 16 Jul 2024 02:26:41 +0000 Received: from mail-oa1-x35.google.com ([2001:4860:4864:20::35]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sTXtm-002GWI-FH for pgsql-general@lists.postgresql.org; Tue, 16 Jul 2024 02:26:40 +0000 Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-25e24900a82so2368113fac.3 for ; Mon, 15 Jul 2024 19:26:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721096797; x=1721701597; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Fz8NRhXIBvJHvSQGdQXQ+qhrznkTnp2DnPJpbsStah0=; b=I9Ez2tsNp/SLCr7/HhXD3b67mPDbWEKhxnSF9h4Ub5ujmaDLu6Dw67W/2e45zqBLeS SNIgBHnMcNodgNBN0amZ80CyscZ6UNzrDRKWYLi2UoDolGi0NalO+7fDHtaycNfb9ORR NgXoSnOBta3s/872/8z8UZdRWoHcSml99e89k2hhcOmebcLBLPUzcNR8BlcXfUWp+OZl pGovy5rQcis6sDlEqDN7+2wLlR9U/4s9IzPrUGquC+dUNRSTzJretcIZ89sEAuYhT4sm 31wifMb6zV1OJbKn67WfR3aCMdY0p6tWqaPxQFKuv510GytxGxWcF2mP8i5y+9VaqufH a0ZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721096797; x=1721701597; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Fz8NRhXIBvJHvSQGdQXQ+qhrznkTnp2DnPJpbsStah0=; b=Jx5FMy0+iSEu0gR0cPJToJSgThdVaWMBjGnuHVnuVtvU3S5Yx7y+quynC5WFqz0t0r +ifT3Z4HWbBurKkf3mpLKNe3AWRlXCiUr/9cmY8CfwhdjDXs76AA+shluDvg+PFR5pKb iPO+yqv0EyyOSg0dIyFhiAltmlAdvvXXwEb/aKOv0e+7D5nZXdPdwmqw+p0KbB5usPrt QRryGnO7aazSEgBPYU42pk7GCR75WGL5HgcppjKZ00lvQhygJGTxglse87XaRbHNPigp NS0+HHOXAioi+oafImNvC1o2hqDRzNwNijElQxvf7IQMz+ZTrKAXHHJyykuXcumnrK/k CC1w== X-Gm-Message-State: AOJu0YyddnQ7yYEu/AXbNkppeBi4HxSMYxNjp/nUVtkn/dYvyn4Hkea8 bR8lzHBmrIX30grOsSQ/CzE4HbTPbUDOomk/fk/Oewv1k3fdkvSLvGt0XVlIcGAhahPuPVkOsft 5oiBJwvNw8m7tkJrz/X3xPfgrvncN9w== X-Google-Smtp-Source: AGHT+IGFFP9fV0X8qBhZPQv4vlAyiS4v9r6sNgwELbzmMDNh1T6/AL+tjDTkUd3bw1aSotSCfAl8SLfZyqiBbTKFxB4= X-Received: by 2002:a05:6870:4687:b0:25e:44eb:6972 with SMTP id 586e51a60fabf-260bd998651mr513412fac.44.1721096797183; Mon, 15 Jul 2024 19:26:37 -0700 (PDT) MIME-Version: 1.0 References: <0BD5E273-8E2C-4EDD-AB13-37CC3309E30E@thebuild.com> In-Reply-To: From: Ron Johnson Date: Mon, 15 Jul 2024 22:26:26 -0400 Message-ID: Subject: Re: PostgreSQL Active-Active Clustering To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000003867ea061d541301" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003867ea061d541301 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jul 15, 2024 at 5:54=E2=80=AFPM Christoph Moench-Tegeder wrote: > ## Ron Johnson (ronljohnsonjr@gmail.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 product= s > > 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. --0000000000003867ea061d541301 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jul 15, 2024 at 5:54=E2=80=AFPM C= hristoph Moench-Tegeder <cmt@burgg= raben.net> wrote:
## Ron Johnson (ronljohnsonjr@gmail.com):

> This "lack of products" puzzles me, because DEC was doing th= is with VAX
> (then Alpha and Itanium) clusters 40 years ago via a Distributed Lock<= br> > Manager integrated deep into VMS.=C2=A0 Their Rdb and (CODASYL) DBMS p= roducts

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<= br> processor" was quite a feat in the 80ies ("A dual processor VAX 1= 1/780",
1982 https://dl.acm.org/doi/10.5555/800048.801738; a= lso 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.

=C2=A0Customers still want High Av= ailability, and VMS Clusters were great for HA.=C2=A0
--0000000000003867ea061d541301--