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

On Mon, Oct 13, 2025 at 5:08 PM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
> 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.

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.