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 1sam4s-00B4Er-Ey for pgsql-bugs@arkaria.postgresql.org; Mon, 05 Aug 2024 00:59:58 +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 1sam4p-00AdGB-J7 for pgsql-bugs@arkaria.postgresql.org; Mon, 05 Aug 2024 00:59:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sam4p-00AdG3-AQ for pgsql-bugs@lists.postgresql.org; Mon, 05 Aug 2024 00:59:55 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sam4m-003606-IC for pgsql-bugs@lists.postgresql.org; Mon, 05 Aug 2024 00:59:53 +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 4750xoPd937526; Sun, 4 Aug 2024 20:59:50 -0400 From: Tom Lane To: "David G. Johnston" cc: =?UTF-8?B?0JDQvdC00YDQtdC5INCg0LDRh9C40YbQutC40Lk=?= , pgsql-bugs@lists.postgresql.org, Robert Haas Subject: Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION In-reply-to: References: <18545-feba138862f19aaa@postgresql.org> <72802.1721415837@sss.pgh.pa.us> <1722241488.182053205@f169.i.mail.ru> <3593204.1722466756@sss.pgh.pa.us> <3618203.1722473994@sss.pgh.pa.us> <916377.1722809337@sss.pgh.pa.us> Comments: In-reply-to "David G. Johnston" message dated "Sun, 04 Aug 2024 17:46:53 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <937524.1722819590.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Sun, 04 Aug 2024 20:59:50 -0400 Message-ID: <937525.1722819590@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > On Sun, Aug 4, 2024 at 3:09 PM Tom Lane wrote: >> Any opinions about whether it's too late to do this in v17? >> Post-beta3 is pretty late, for sure, but maybe we could get >> away with it. And we are fixing a bug here. > If this isn't going to appear in the beta3 build I'd say it's probably too > late given the target audience for waiting on this is extension authors. > If it is going into beta3 then I'd vote to allow it. Nope, it's definitely not going into beta3; it's about two days too late for that. I agree fixing it in HEAD only is the more conservative course. To do otherwise, we'd have to rank the #18545 bug as fairly important, and I'm not sure I buy that given how long it took to notice it. But I was curious to see if anyone felt differently. regards, tom lane