From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dominique Devienne <ddevienne@gmail.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: veem v <veema0000@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: Moving to Postgresql database
Date: Tue, 16 Jan 2024 16:59:10 -0500
Message-ID: <1904120.1705442350@sss.pgh.pa.us> (raw)
In-Reply-To: <CAFCRh-_hkHF1oEDRdEJnOXSz=RzXruzdpq3jdxvZ25fWLcqpbA@mail.gmail.com>
References: <CAB+=1TUyxXeRbmz6oRC+96EjLAnW7Qvqmse4iSNtWgH5i21mQg@mail.gmail.com>
<CAFCRh-9qkLTCWPssN4ZOvGj3JY3LceMKs2eaizx49b2Cx8019Q@mail.gmail.com>
<40a34680-1583-4cff-86cb-2598be16bb80@aklaver.com>
<CAFCRh-9Es2Ahgzetyu-46guwyGwPjaJXHfGpF0AG4zt7KDBjfw@mail.gmail.com>
<8cbd791a-0688-49fb-a536-3b8c30b5109b@aklaver.com>
<CAFCRh-_hkHF1oEDRdEJnOXSz=RzXruzdpq3jdxvZ25fWLcqpbA@mail.gmail.com>
Dominique Devienne <ddevienne@gmail.com> writes:
> But sure, I take your point, you can emulate statement-level (implicit)
> rollback via an explicit SAVEPOINT, and ROLLBACK to the savepoint instead.
> But my point remains, that something like what that extension does should
> be an option of PostgreSQL itself, not an extension. --DD
> PS: I'd also be happy to hear why it's not, or won't be, on technical terms.
The reason it's not going to happen is that the community (or at least
the more senior developers) still remembers what happened the last
time we tried it.
We did implement server-side auto-rollback years ago in PG 7.3,
and it was enough of a disaster that we took it out again in 7.4.
The problem is that now you have a switch somewhere (whether a GUC
or something else, still a switch) that fundamentally changes the
transactional semantics seen by applications. Run an application
in the wrong mode and you have a broken app. Worse, there is an
awful lot of client-side code that now has to cope with both
behaviors. We thought that would be okay ... well, it wasn't.
It was a mess. It would be a bigger mess now if we were to try it
again, because there would be even more broken client code.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, ddevienne@gmail.com, adrian.klaver@aklaver.com, veema0000@gmail.com
Subject: Re: Moving to Postgresql database
In-Reply-To: <1904120.1705442350@sss.pgh.pa.us>
References: <CAB+=1TUyxXeRbmz6oRC+96EjLAnW7Qvqmse4iSNtWgH5i21mQg@mail.gmail.com> <CAFCRh-9qkLTCWPssN4ZOvGj3JY3LceMKs2eaizx49b2Cx8019Q@mail.gmail.com> <40a34680-1583-4cff-86cb-2598be16bb80@aklaver.com> <CAFCRh-9Es2Ahgzetyu-46guwyGwPjaJXHfGpF0AG4zt7KDBjfw@mail.gmail.com> <8cbd791a-0688-49fb-a536-3b8c30b5109b@aklaver.com> <CAFCRh-_hkHF1oEDRdEJnOXSz=RzXruzdpq3jdxvZ25fWLcqpbA@mail.gmail.com> <1904120.1705442350@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox