Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1ocfPS-0006O7-0X
	for pgsql-bugs@arkaria.postgresql.org; Mon, 26 Sep 2022 04:07:58 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1ocfPQ-0003sd-BT
	for pgsql-bugs@arkaria.postgresql.org; Mon, 26 Sep 2022 04:07:56 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1ocfPQ-0003sU-3Z
	for pgsql-bugs@lists.postgresql.org; Mon, 26 Sep 2022 04:07:56 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1ocfPN-0002Wv-Rh
	for pgsql-bugs@lists.postgresql.org; Mon, 26 Sep 2022 04:07:55 +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 28Q47otC3268291;
	Mon, 26 Sep 2022 00:07:50 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: Masahiko Sawada <sawada.mshk@gmail.com>,
        Justin Pryzby <pryzby@telsasoft.com>,
        Dmitry Koval <d.koval@postgrespro.ru>,
        Dilip Kumar <dilipbalaut@gmail.com>, andrewbille@gmail.com,
        pgsql-bugs@lists.postgresql.org,
        Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Subject: Re: BUG #17385: "RESET transaction_isolation" inside serializable
 transaction causes Assert at the transaction end
In-reply-to: <YzEfR9UUb3gqRjoA@paquier.xyz>
References: 
 <CAD21AoDWHkBBGvvJuLEBqMjiPiYOiVJ6voFBWYbOBsU+-Cot2A@mail.gmail.com>
 <20220628003720.GG19662@telsasoft.com>
 <CAD21AoBz4xZ3uOZS+xYENsYta4PPPkGYPDzzPqqw5GJgrQC7hg@mail.gmail.com>
 <Yrv1nRsfasco768G@paquier.xyz>
 <CAD21AoC8FQqHY8knG7+6-eQe39wjXPtqyki29OAb5OHhq7-p+Q@mail.gmail.com>
 <CAD21AoD6n62NXB5OuYSONYHKNkR=fqvJ5+82y=4Z=-KuFeOV0w@mail.gmail.com>
 <2604497.1664053071@sss.pgh.pa.us> <YzEfR9UUb3gqRjoA@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
	message dated "Mon, 26 Sep 2022 12:40:55 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3268289.1664165270.1@sss.pgh.pa.us>
Date: Mon, 26 Sep 2022 00:07:50 -0400
Message-ID: <3268290.1664165270@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/3268290.1664165270%40sss.pgh.pa.us>
Precedence: bulk

Michael Paquier <michael@paquier.xyz> writes:
> Just to be sure about something here.  The change of behavior with SET
> in the context of a PL makes this patch unsuitable for a backpatch,
> hence the plan is to apply this stuff only on HEAD, right? 

Yeah, I think we concluded that back-patching might cause more
trouble than it's worth.

> +      <entry><literal>NO_RESET</literal></entry>
> +      <entry>Parameters with this flag do not support
> +      <command>RESET</command> commands.
> +      </entry>

> As per the issue with SET commands used with functions, this
> description does not completely reflect the reality.

It seems adequate enough to me ... do you have a suggestion?

			regards, tom lane