Request a Demo
Home   >   mailing lists

Re: Option on `postgres` CLI to shutdown when there are no more active connections? - Mailing list pgsql-general

From Ron Johnson
Subject Re: Option on `postgres` CLI to shutdown when there are no more active connections?
Date
Msg-id CANzqJaDn_mVi4M0CbKnVNwK9RxYOneoCRmd_d69rbjBrwasuPQ@mail.gmail.com
Whole thread Raw
In response to Re: Option on `postgres` CLI to shutdown when there are no more active connections?  (Dominique Devienne <ddevienne@gmail.com>)
Responses Re: Option on `postgres` CLI to shutdown when there are no more active connections?
List pgsql-general
Tree view
On Mon, Oct 13, 2025 at 4:47 AM Dominique Devienne <ddevienne@gmail.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!

pgsql-general by date:

Previous
From: Dominique Devienne
Date:
Subject: Re: Option on `postgres` CLI to shutdown when there are no more active connections?
Next
From: Dominique Devienne
Date:
Subject: Re: Option on `postgres` CLI to shutdown when there are no more active connections?