Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sZIHz-00HZms-Ce for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Jul 2024 22:59:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sZIHx-00FW1k-Lm for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Jul 2024 22:59:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sZIHx-00FW1c-Dm for pgsql-bugs@lists.postgresql.org; Wed, 31 Jul 2024 22:59:21 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sZIHv-002Vcj-78 for pgsql-bugs@lists.postgresql.org; Wed, 31 Jul 2024 22:59:20 +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 46VMxGTG3593205; Wed, 31 Jul 2024 18:59:17 -0400 From: Tom Lane To: =?UTF-8?B?0JDQvdC00YDQtdC5INCg0LDRh9C40YbQutC40Lk=?= cc: pgsql-bugs@lists.postgresql.org, =?UTF-8?B?Um9iZXJ0IEhhYXM=?= Subject: Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION 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> Comments: In-reply-to =?UTF-8?B?0JDQvdC00YDQtdC5INCg0LDRh9C40YbQutC40Lk=?= message dated "Mon, 29 Jul 2024 11:24:48 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3593203.1722466756.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 31 Jul 2024 18:59:16 -0400 Message-ID: <3593204.1722466756@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =3D?UTF-8?B?0JDQvdC00YDQtdC5INCg0LDRh9C40YbQutC40Lk=3D?=3D writes: > Hi, Tom!=C2=A0Thank you for work on the subject.=C2=A0 After applying pa= tch, 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