On Wed, Feb 16, 2022 at 1:55 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Masahiko Sawada <sawada.mshk@gmail.com> writes:
> > It seems that we need another flag or a dedicated treatment for
> > transaction property GUCs. It effectively cannot change them within
> > the transaction regardless of SET, RESET, and RESET ALL, so I think we
> > can make it no-op (possibly with a notice).
>
> Yeah, I was considering that too. A new GUC_NO_RESET flag would be
> cheaper than running the check hooks during RESET, and probably
> safer too. On the other hand, we would lose the property that
> you can reset these settings as long as you've not yet taken a
> snapshot. I wonder whether there is any code out there that
> depends on that ...
Indeed. I guess that it's relatively common that the transaction
isolation level is set after BEGIN TRANSACTION but I've not heard that
it's reset after BEGIN TRANSACTION with setting non-default
transaction isolation level.
Regards,
--
Masahiko Sawada
EDB: https://www.enterprisedb.com/
