pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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: Wed, 17 Jan 2024 10:33:49 -0500
Message-ID: <2029740.1705505629@sss.pgh.pa.us> (raw)
In-Reply-To: <CAFCRh-9RYHczWVJnfcb_-iMHkA9L3-tp0s-o9WNV3h4+QmLNaw@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>
	<1904120.1705442350@sss.pgh.pa.us>
	<CAFCRh-9RYHczWVJnfcb_-iMHkA9L3-tp0s-o9WNV3h4+QmLNaw@mail.gmail.com>

Dominique Devienne <ddevienne@gmail.com> writes:
> On Tue, Jan 16, 2024 at 10:59 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

> OK. That speaks against making it the default for sure.
> But what if the client-code explicitly opts-in to that mode/switch?

It wasn't default in 7.3, either.

The key point here is that "the client code" isn't monolithic:
there are frequently 3 or 4 layers involved, all maintained by
different sets of people.  If any one of them chooses to flip the
switch, all of them have to cope with the results (possibly without
even having observed the change).  Like I said, it was a mess.

Perhaps we could have got away with changing this back around 1997.
By the time we tried (7.3 was released in 2002), it was already
too late because of the amount of client-side code that needed to
change and couldn't change in a timely fashion.  Twenty years
later, that situation has to be many times worse.

> Basically implicit-statement-level-rollback is the norm, AFAIK, and
> PostgreSQL is the exception here.

I'm well aware of that.  It doesn't matter.

			regards, tom lane





view thread (18+ messages)  latest in thread

Message-ID: <2029740.1705505629@sss.pgh.pa.us>
Permalink:  ../2029740.1705505629@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2029740.1705505629@sss.pgh.pa.us

 · 

reply

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: <2029740.1705505629@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> <CAFCRh-9RYHczWVJnfcb_-iMHkA9L3-tp0s-o9WNV3h4+QmLNaw@mail.gmail.com> <2029740.1705505629@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