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

From Tom Lane
Subject Re: Option on `postgres` CLI to shutdown when there are no more active connections?
Date
Msg-id 233155.1760369829@sss.pgh.pa.us
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
Dominique Devienne <ddevienne@gmail.com> writes:
> On Mon, Oct 13, 2025 at 5:08 PM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
>> 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 has accepted the cost that comes with being embedded, which is
that application-side memory-stomping bugs can destroy the database.
Postgres is not willing to make that tradeoff.  From a pure
developer's perspective, every time we got a bug report we'd have to
ask "did you observe this while running embedded?" and then demand a
repro that uses a non-embedded database.  We are not going to help
application authors debug their own bugs, especially not when we have
no visibility into what those are.

> SQLite is also ACID.

I guess they have a different set of assumptions about what that
buzzword means.

            regards, tom lane



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: Ashish Mukherjee
Date:
Subject: Enquiry about TDE with PgSQL