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 <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1s36Qo-009SFY-I8
	for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 03:51:26 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1s36Ql-00EkH0-RG
	for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 03:51:24 +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 <tgl@sss.pgh.pa.us>)
	id 1s36Ql-00EkG4-GF
	for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 03:51:24 +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 <tgl@sss.pgh.pa.us>)
	id 1s36Qj-001Rfz-Pl
	for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 03:51:23 +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 4443pHgw2808876;
	Fri, 3 May 2024 23:51:17 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: jian he <jian.universality@gmail.com>
cc: Adrian Klaver <adrian.klaver@aklaver.com>,
        Magnus Hagander <magnus@hagander.net>,
        David Gauthier <dfgpostgres@gmail.com>,
        pgsql-general@lists.postgresql.org
Subject: Re: \dt shows table but \d <table> says the table doesn't exist ?
In-reply-to: <CACJufxF=VJ=wprULGXLuAaSt5j+4w0=66HzKDQ9GEKFXMo1-bg@mail.gmail.com>
References: <CAEs=6DnMQCAF_c+=Vup8qnOM1OT1GfFq6nzGF2a3EhgnyrjpMg@mail.gmail.com> <CABUevEwkSS_FhL0Zi1_m3oU5WqELHF+qQfCLDK3e__qTsYdsYw@mail.gmail.com> <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> <2746167.1714770911@sss.pgh.pa.us> <CACJufxF=VJ=wprULGXLuAaSt5j+4w0=66HzKDQ9GEKFXMo1-bg@mail.gmail.com>
Comments: In-reply-to jian he <jian.universality@gmail.com>
	message dated "Sat, 04 May 2024 11:40:56 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2808874.1714794677.1@sss.pgh.pa.us>
Date: Fri, 03 May 2024 23:51:17 -0400
Message-ID: <2808875.1714794677@sss.pgh.pa.us>
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/2808875.1714794677%40sss.pgh.pa.us>
Precedence: bulk

jian he <jian.universality@gmail.com> writes:
> make it case insensitive?

That would just move the problem around; that is, now we'd have people
complaining because they'd asked for "\d foo" and were getting results
for tables Foo and FOO.

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.

			regards, tom lane