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.96) (envelope-from ) id 1wX8RB-0034ip-0b for pgsql-hackers@arkaria.postgresql.org; Wed, 10 Jun 2026 02:13:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wX8RA-008qRr-0L for pgsql-hackers@arkaria.postgresql.org; Wed, 10 Jun 2026 02:13:00 +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.96) (envelope-from ) id 1wX8R9-008qRj-29 for pgsql-hackers@lists.postgresql.org; Wed, 10 Jun 2026 02:12:59 +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.98.2) (envelope-from ) id 1wX8R7-00000002Fm0-1NLZ for pgsql-hackers@lists.postgresql.org; Wed, 10 Jun 2026 02:12:59 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 65A2CmJ71236174; Tue, 9 Jun 2026 22:12:48 -0400 From: Tom Lane To: Michael Paquier cc: Bertrand Drouvot , Chao Li , Postgres hackers , Fujii Masao , Peter Eisentraut , Jeff Davis , Ashutosh Bapat , Amit Kapila Subject: Re: Fix unqualified catalog references in psql describe queries In-reply-to: References: Comments: In-reply-to Michael Paquier message dated "Wed, 10 Jun 2026 10:57:16 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1236172.1781057568.1@sss.pgh.pa.us> Date: Tue, 09 Jun 2026 22:12:48 -0400 Message-ID: <1236173.1781057568@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > On Tue, Jun 09, 2026 at 09:08:50AM +0000, Bertrand Drouvot wrote: >> Now I wonder if we shoud not "protect" the operators too. They could also >> lead to wrong results (if not worst). > Kind of true. Still we have been pretty lax about the operators as > they also lead to less readable queries. We disclaimed security against odd search_paths for these queries long ago, precisely because wrapping every operator in PG_OPERATOR(pg_catalog.*) would be far too tedious and destructive of readability --- not to mention that there are some syntaxes such as IN that don't even offer the option to do that. I'm okay with schema-qualifying these table references, mainly because that preserves consistency with historical style here. But let's not go further than that. regards, tom lane