From: Tom Lane <tgl@sss.pgh.pa.us>
To: Андрей Рачицкий <therealgofman@mail.ru>
Cc: pgsql-bugs@lists.postgresql.org, Robert Haas <robertmhaas@gmail.com>
Subject: Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
Date: Wed, 31 Jul 2024 18:59:16 -0400
Message-ID: <3593204.1722466756@sss.pgh.pa.us> (raw)
In-Reply-To: <1722241488.182053205@f169.i.mail.ru>
References: <18545-feba138862f19aaa@postgresql.org>
<72802.1721415837@sss.pgh.pa.us>
<1722241488.182053205@f169.i.mail.ru>
=?UTF-8?B?0JDQvdC00YDQtdC5INCg0LDRh9C40YbQutC40Lk=?= <therealgofman@mail.ru> writes:
> Hi, Tom! Thank you for work on the subject. After applying patch, problem is no longer reproducible.
Thanks for checking. I realized that the idea of making
check_session_authorization a no-op was wrong as presented:
if we don't set up an "extra" struct then guc.c would be
unable to restore the setting later, in case say a function
that's run inside the parallel query has a SET
session_authorization clause. It's probably possible to
revive that idea with more work, but it's not essential to the
bug fix and we're getting close to the August minor releases.
So I pushed the core bug fix, and I'll take another look at
that part later.
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 using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, therealgofman@mail.ru, robertmhaas@gmail.com
Subject: Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
In-Reply-To: <3593204.1722466756@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