Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v8Kc2-00GSML-8E for pgsql-general@arkaria.postgresql.org; Mon, 13 Oct 2025 15:37:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v8Kc0-006bja-1a for pgsql-general@arkaria.postgresql.org; Mon, 13 Oct 2025 15:37:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v8Kbz-006bjR-Mz for pgsql-general@lists.postgresql.org; Mon, 13 Oct 2025 15:37:24 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1v8Kbn-001x87-0M for pgsql-general@lists.postgresql.org; Mon, 13 Oct 2025 15:37:24 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 59DFb9eX233156; Mon, 13 Oct 2025 11:37:09 -0400 From: Tom Lane To: Dominique Devienne cc: Ron Johnson , "pgsql-generallists.postgresql.org" Subject: Re: Option on `postgres` CLI to shutdown when there are no more active connections? In-reply-to: References: <73ff46d2-0bad-4a8d-9928-e494c2d5b0d1@gmail.com> <93702.1760321769@sss.pgh.pa.us> Comments: In-reply-to Dominique Devienne message dated "Mon, 13 Oct 2025 17:15:20 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <233154.1760369829.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 13 Oct 2025 11:37:09 -0400 Message-ID: <233155.1760369829@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Dominique Devienne writes: > On Mon, Oct 13, 2025 at 5:08=E2=80=AFPM Ron Johnson wrote: >> Shared memory means that I can stomp all over you, and you can't stop m= e. 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