Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n6HwL-00029i-AQ for pgsql-hackers@arkaria.postgresql.org; Sat, 08 Jan 2022 20:03:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n6HwJ-0002ik-TK for pgsql-hackers@arkaria.postgresql.org; Sat, 08 Jan 2022 20:03:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n6HwJ-0002iY-KT for pgsql-hackers@lists.postgresql.org; Sat, 08 Jan 2022 20:03:47 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n6HwH-0002wS-Dm for pgsql-hackers@lists.postgresql.org; Sat, 08 Jan 2022 20:03:46 +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 208K3dhC1581831; Sat, 8 Jan 2022 15:03:40 -0500 From: Tom Lane To: =?utf-8?Q?=C3=81lvaro?= Herrera cc: Michael Paquier , Justin Pryzby , Tatsuro Yamada , Magnus Hagander , pgsql-hackers@lists.postgresql.org, Tomas Vondra , pgsql-hackers@postgresql.org Subject: Re: \dP and \dX use ::regclass without "pg_catalog." In-reply-to: <202201081950.teiyz4ic43oi@alvherre.pgsql> References: <202201081950.teiyz4ic43oi@alvherre.pgsql> Comments: In-reply-to =?utf-8?Q?=C3=81lvaro?= Herrera message dated "Sat, 08 Jan 2022 16:50:19 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1581829.1641672219.1@sss.pgh.pa.us> Date: Sat, 08 Jan 2022 15:03:39 -0500 Message-ID: <1581830.1641672219@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =?utf-8?Q?=C3=81lvaro?= Herrera writes: > My point is that it's good to have it, but it would be much better to > have something bulletproof, which we could use in an automated check > somewhere (next to stuff like perlcritic, perhaps). I don't know what, > though. Meh ... this is mostly cosmetic these days, so I can't get excited about putting a lot of work into it. We disclaimed search path bulletproofness for all these queries a long time ago. I don't object to fixing it in the name of consistency, but that's not a reason to invest large effort. regards, tom lane