Re: Option on `postgres` CLI to shutdown when there are no more active connections?

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: Option on `postgres` CLI to shutdown when there are no more active connections?
Date: 2025-10-13 15:07:53
Message-ID: CANzqJaDn_mVi4M0CbKnVNwK9RxYOneoCRmd_d69rbjBrwasuPQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Oct 13, 2025 at 4:47 AM Dominique Devienne <ddevienne(at)gmail(dot)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.

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

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dominique Devienne 2025-10-13 15:15:20 Re: Option on `postgres` CLI to shutdown when there are no more active connections?
Previous Message Dominique Devienne 2025-10-13 08:47:22 Re: Option on `postgres` CLI to shutdown when there are no more active connections?