MIME-Version: 1.0
References: <CAPR5_5psNqCm1OQr5LL4v6z02Sh=2YHYUg8NY+3xMzfGHfKs+w@mail.gmail.com>
 <ea93ff28-4496-4e3d-a529-191582e02344@aklaver.com> <CAPR5_5q2oCkw19rHb7oy-M0M0purWFM5Jc8ub5xDy_NdhUmRTw@mail.gmail.com>
 <73ff46d2-0bad-4a8d-9928-e494c2d5b0d1@gmail.com> <93702.1760321769@sss.pgh.pa.us>
 <CAFCRh-94eXetAjtCURs5F0JZQr=kso0rVgVSEmWiSD7wA6VcMw@mail.gmail.com> <CANzqJaDn_mVi4M0CbKnVNwK9RxYOneoCRmd_d69rbjBrwasuPQ@mail.gmail.com>
In-Reply-To: <CANzqJaDn_mVi4M0CbKnVNwK9RxYOneoCRmd_d69rbjBrwasuPQ@mail.gmail.com>
From: Dominique Devienne <ddevienne@gmail.com>
Date: Mon, 13 Oct 2025 17:15:20 +0200
Message-ID: <CAFCRh--P93bF0gpkdvg4MzMNqq5gK=4eWFkmBDR0xw9dmFVAPQ@mail.gmail.com>
Subject: Re: Option on `postgres` CLI to shutdown when there are no more
 active connections?
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAFCRh--P93bF0gpkdvg4MzMNqq5gK%3D4eWFkmBDR0xw9dmFVAPQ%40mail.gmail.com>
Precedence: bulk

On Mon, Oct 13, 2025 at 5:08=E2=80=AFPM Ron Johnson <ronljohnsonjr@gmail.co=
m> wrote:
> On Mon, Oct 13, 2025 at 4:47=E2=80=AFAM Dominique Devienne <ddevienne@gma=
il.com> wrote:
> [snip]
>> There's apparently no way to abstract the "transport" between libpq
>> and the server, must be TCP (or *nix only socket files), cannot be an
>> in-memory channel (for the embedded non-shared case),
> I'd bet a nickel that local socket transfers all stay in memory.

But that's not cross-platform... Needs to work the same on Windows.

>> nor shared-memory (for the shared-case across localhost processes).
> Shared memory means that I can stomp all over you, and you can't stop me.=
  That's the antithesis of ACID.

SHM is how SQLite in WAL mode coordinates access to the same DB from
several connections. So if it's good enough for SQLite, I don't see
what it would be wrong for PostgreSQL too. SQLite is also ACID.