Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end
Date
Msg-id Yrv1nRsfasco768G@paquier.xyz
Whole thread Raw
In response to Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-bugs
On Tue, Jun 28, 2022 at 03:58:41PM +0900, Masahiko Sawada wrote:
> Agreed. I've attached an updated patch.

+#define GUC_NO_RESET         0x400000  /* not support RESET and save */

It is a bit sad to see this new flag with this number, separated from
its cousin properties.  Could it be better to reorganize the flag
values and give more room to the properties?  The units for memory and
time could go first, for example.

+CREATE FUNCTION errfunc() RETURNS int LANGUAGE SQL AS 'SELECT 1'
+SET transaction_read_only = on; -- error
+ERROR:  parameter "transaction_read_only" cannot be reset
Well, this is confusing when setting a GUC_NO_RESET in the context of
GUC_ACTION_SAVE.

By the way, what about "seed"?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: David Johansen
Date:
Subject: Re: Auto-vacuum timing out and preventing connections
Next
From: Masahiko Sawada
Date:
Subject: Re: Auto-vacuum timing out and preventing connections