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 1s36nA-009Vxv-UD for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:14:32 +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 1s36n7-00Ew8R-2G for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:14:29 +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 1s36n6-00Ew8J-Nu for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:14:29 +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 1s36n5-001LPa-4T for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:14:28 +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 4444ENDR2816867; Sat, 4 May 2024 00:14:23 -0400 From: Tom Lane To: "David G. Johnston" cc: jian he , Adrian Klaver , Magnus Hagander , David Gauthier , "pgsql-general@lists.postgresql.org" Subject: Re: \dt shows table but \d says the table doesn't exist ? In-reply-to: References: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> <2746167.1714770911@sss.pgh.pa.us> <2808875.1714794677@sss.pgh.pa.us> Comments: In-reply-to "David G. Johnston" message dated "Fri, 03 May 2024 21:06:20 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2816865.1714796063.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sat, 04 May 2024 00:14:23 -0400 Message-ID: <2816866.1714796063@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 Friday, May 3, 2024, Tom Lane wrote: >> By and large, I'd expect people using mixed-case table names to get >> accustomed pretty quickly to the fact that they have to double-quote >> those names in SQL. I don't see why it's a surprise that that is also >> true in \d commands. > Every day the number of people increases who get mixed-case names in the= ir > DB because their client language preserves case and doesn=E2=80=99t requ= ire quoting. And? If they access the DB exclusively through their client language, then yeah maybe they'll never know the difference. But if they are also using psql or other direct-SQL-access tools, they will learn the quoting rules PDQ. There's still no reason that \d should be inconsistent with SQL. regards, tom lane