From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
Cc: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, "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:37:09 |
Message-ID: | 233155.1760369829@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dominique Devienne <ddevienne(at)gmail(dot)com> writes:
> On Mon, Oct 13, 2025 at 5:08 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ashish Mukherjee | 2025-10-13 15:55:27 | Enquiry about TDE with PgSQL |
Previous Message | Dominique Devienne | 2025-10-13 15:15:20 | Re: Option on `postgres` CLI to shutdown when there are no more active connections? |