From dfgpostgres@gmail.com Fri May 15 23:21:46 2026 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 1s2zzQ-008Fxi-U1 for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 20:58:44 +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 1s2zzO-00Buvw-1m for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 20:58:42 +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 ) id 1s2zzN-00Buvm-N9 for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 20:58:42 +0000 Received: from mail-pg1-x52e.google.com ([2607:f8b0:4864:20::52e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s2zzM-001Okm-7K for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 20:58:42 +0000 Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-5e152c757a5so49604a12.2 for ; Fri, 03 May 2024 13:58:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714769917; x=1715374717; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=E8Orj9IMv+O5yAUpamf+jyxDbl4uaJrID/ogIfEDXE0=; b=L+6MC7BkWHLIQNCqev0sXidZgh4EVWoHln+eaJpiCWvozpu7JWG8fAQIsoh1cKqvwz JXkcm7fk+FIQ3Vv61xQVyneTQWgTVg8zSyhklttiX/e+O2rkIS3Mkyfly6R3Douw/YVJ 5CRD8LwtRrS/DXs7hRWYrRe2q6jbk3BRTV2L2S73bRH6U9boW48ru45ZXS3t1eQv93N5 CfSgUmNo3fnvARwHLpW84ctql3lnscLj+pn6SShyN8neVcROSaaUgBbS5KT1q93DLl98 grZn84J9pS3O53SCjDUszGiLKEY5Gpr4Fl0mPrM3cXXfX8Pr2wOwYFYHRIhvmNZHGUno f59A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714769917; x=1715374717; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=E8Orj9IMv+O5yAUpamf+jyxDbl4uaJrID/ogIfEDXE0=; b=T92CxVtMIk2aa3kdy5e8Ju+3yOZoPL9zAHF0FU/4OcefzP1ybCt5Ok156ntLKZpO1d 1oBoBx4WVXbSoPoMiO4+on+wmErCCKjCB3sJoNCdo4xgcTLBH7UQCdJP8xvTybcHPl9C 71lJnq2buWs/jG/wtIxUm3kSBHL1q8kYoe3eZSBkt6oSNb5qYG96fQrKVbtVoooLKAW3 oOTRMg+2burOVvU6qV3y7AynpdmcgYfysqeq7da/818F3lsQ28/U8cfOJjFf0fIjEP3L vjVQ4oXRtK0TOdpgxdWNQxgZG6sT6DkrtyQCnkht5icfVS/HZBsHUpNKkFzteMlmtePt 1D1w== X-Gm-Message-State: AOJu0Yxa6G2y+cpyOmcqmZsnopwirFAcAVXARscJBvO0d6oCmzZSvhDS FZA4da0lcgvtc1T+o6smlUe5Kua16Q2+AsfNDibJwGsmjPji23UjlbceysbpANsBjx9OQYOKzKT Sx4jK3AUr7Wlh+SrdiCSFs/5e7jMjVkj3 X-Google-Smtp-Source: AGHT+IEREiq8qKoNjq+upj7somMY8eoMx5hhsKBh2P28zShPDjeIOcfrL2nDGk3fJ5OCwSqtCS/YYWK5iFLJ6eoiEy4= X-Received: by 2002:a17:90b:80a:b0:2b4:8eb6:895f with SMTP id bk10-20020a17090b080a00b002b48eb6895fmr1106021pjb.16.1714769917339; Fri, 03 May 2024 13:58:37 -0700 (PDT) MIME-Version: 1.0 From: David Gauthier Date: Fri, 3 May 2024 16:58:26 -0400 Message-ID: Subject: \dt shows table but \d says the table doesn't exist ? To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000cb71aa061792fb3a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000cb71aa061792fb3a Content-Type: text/plain; charset="UTF-8" psql (15.3, server 14.5) on linux Someone else's DB which I've been asked to look at. \dt gives many tables, here are just 3... public | some_idIds | table | cron_user public | WarningIds | table | cron_user public | cpf_inv_driverIds | table | cron_user but \d public.some_idIds gives.. Did not find any relation named "public.some_idIds". Soooooo... what am I missing ? owner is "cron_user". \dt shows cron_user is the owner of the table. --000000000000cb71aa061792fb3a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
psql (15.3, server 14.5) on linux

S= omeone else's DB which I've been asked to look at.

\dt gives many tables, here are just 3...

=C2=A0public | some_idIds =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 | table | cron_user
=C2=A0public | WarningIds =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | table | cron_user=
=C2=A0public | cpf_inv_driverIds =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0| table | cron_user

but \d public.so= me_idIds gives..

Did not find any relation named &= quot;public.some_idIds".

Soooooo... what = am I missing ?
owner is "cron_user".=C2=A0 \dt shows cron_user= is the owner of the table.


--000000000000cb71aa061792fb3a-- From magnus@hagander.net Fri May 15 23:22:36 2026 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 1s3071-008HCD-S6 for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:06:35 +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 1s306y-00BzQP-0v for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:06:32 +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 ) id 1s306x-00BzQF-Kr for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:06:32 +0000 Received: from mail-pf1-x435.google.com ([2607:f8b0:4864:20::435]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s306r-001OnE-2e for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:06:31 +0000 Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-6f28bb6d747so126008b3a.3 for ; Fri, 03 May 2024 14:06:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander.net; s=mail; t=1714770382; x=1715375182; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zA8iuvvkl1aZfKOMlqljWIRxBYNLIFnW1Rab81QXeWY=; b=ZaJ2WcnZF8Z657IJVJ5vWcYQX9dzuK5OMMp3GPbmd1OLsHoA48ddABrvi4RaC93RNx Iv/oWuBZllLZVRvX1cTjiD5ILDvR0vPQuhkUR+hQ8+xzUj4crfPHa+SGABbEyg5zqL+r yH2jsl3SnHU/1jFWCGDK2DTYg0+3iyer/dYi+OGZqY+Eiz2xMdUQC3QJajf14bgUXTXd ZAMG3+FpfZRNfQj1KNgf+SvlcaONuBWaVtFTfHke4D56or1oC2F2CQUjWNuIsPUKFA5W GYFpI/EL192RPg0ZMA19BWIxKXFwEjRP6xGVOZX/L0N6dK2QYRK0C0pjX1urqF4fJPXg sWIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714770382; x=1715375182; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zA8iuvvkl1aZfKOMlqljWIRxBYNLIFnW1Rab81QXeWY=; b=u5HgLM68a1oJXtt0DO1wWdgVlSBaPS3oKqedIKjuQVeUaInNzYiRSWghzbWZvcAxtV mxAXNwrrbmGIiYw3DZI/gWHouLiACe0/IdKEHqGYIrSH8lk3zXVrLWCm/mUb9iz5yNn2 u6WQiDHffshTA1wh43NvG++ymc7AV7xco4ELzYDBc5V0acs0JDLSIBr7zpovcMtQYSks EBolaK7AgO1Yv0r7XGDz8LmLaGrNjK/dvhWcvfSN7KxWlroycuSS6Kv6+SYuvofaEjmW pnbQmxDsOf/EPI721k262SayErJSt3/9tpOXdSySJ4Z6dUhXP2OSgos1IbCRuaRR+xVG j6KA== X-Gm-Message-State: AOJu0YzEAJQ3EuN6eljPBYFdb3A1LhnYh/Rph32E5FQ1ftxGKrqZaUCt dHbUkXIrcbZWNlWleq8P5QV3hshWmrbUyf67lW302vOwfYlCrvEPuH+JRJpt/7RICM6tGObt66X O6tVR+56wsMXEvu3kOQdTQLdd2EPzAbJQuPsf X-Google-Smtp-Source: AGHT+IH17GfSgR6TgSNBSlGtOweFLMnuOJp7dNWuyfRWbbsixSV0DSGoK0cGeZ/QTcJKe3yw87Y2zbCpoNhhaROi7vU= X-Received: by 2002:a05:6300:8086:b0:1aa:41e4:f1b4 with SMTP id ap6-20020a056300808600b001aa41e4f1b4mr4153773pzc.44.1714770382558; Fri, 03 May 2024 14:06:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Magnus Hagander Date: Fri, 3 May 2024 23:06:10 +0200 Message-ID: Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: David Gauthier Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000008638ea06179317d8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008638ea06179317d8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, May 3, 2024 at 10:58=E2=80=AFPM David Gauthier wrote: > psql (15.3, server 14.5) on linux > > Someone else's DB which I've been asked to look at. > > \dt gives many tables, here are just 3... > > public | some_idIds | table | > cron_user > public | WarningIds | table | > cron_user > public | cpf_inv_driverIds | table | > cron_user > > but \d public.some_idIds gives.. > > Did not find any relation named "public.some_idIds". > Looks like you might need a \d "some_idIds" (include the quotes) since it has an uppercase characters? --=20 Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --0000000000008638ea06179317d8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, May 3, 2024 at 10:58=E2=80=AF= PM David Gauthier <dfgpostgres@= gmail.com> wrote:
psql (15.3, server 14.5) on linux

<= /div>
Someone else's DB which I've been asked to look at.
=

\dt gives many tables, here are just 3...
=C2=A0public | some_idIds =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 | table | cron_user
=C2=A0public | W= arningIds =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | tab= le | cron_user
=C2=A0public | cpf_inv_driverIds =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0| table | cron_user

bu= t \d public.some_idIds gives..

Did not find any re= lation named "public.some_idIds".


Looks like you might need a \d "some_i= dIds" (include the quotes) since it has an uppercase characters?
=

--
<= div dir=3D"ltr" class=3D"gmail_signature">
=C2=A0Magnu= s Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-linpro.com/
--0000000000008638ea06179317d8-- From adrian.klaver@aklaver.com Fri May 15 23:22:01 2026 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 1s307H-008HEo-I9 for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:06:52 +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 1s307F-00C2Kh-3b for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:06:50 +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 ) id 1s307D-00C2Jv-7m for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:06:49 +0000 Received: from wfhigh7-smtp.messagingengine.com ([64.147.123.158]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s307A-001OnR-0b for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:06:47 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfhigh.west.internal (Postfix) with ESMTP id AC62E180008E; Fri, 3 May 2024 17:06:40 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 03 May 2024 17:06:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1714770400; x=1714856800; bh=R7oLp58eUMJ/+siPiuZyRh9EfdaO0lqeDphjwdrOHws=; b= MwB18cIJlAsuMZ+4baJVw4vF7YELcKyo/ZiVklNRTRt5uqjC1xwuxstAgr62WRSR k07uVb25oTtsxd9V0Q/IZHYMrJ1VYz8vn1YxDeLmOliB6XPNKxvtia08360Nl2PX b50Av9h+71DyrA7E7p2+Plz23RzaDYQPDfvnwuAWpLvnJ2GAymow/KQzMwjmE/+f vJWKWedvCd3VlNWDRVj1LXMCf+WJqUGg0+rugnWthlqdLvAArstT/Wkc5Z/m5lH3 IsGMo5N2zBH7mxXN14M64Pmuv8n7xbIS+Ak7Me5pt5eeVrgnutkjYfsM4ySJH/2Y CcURKE7xe50N5E3nCSBRfw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1714770400; x= 1714856800; bh=R7oLp58eUMJ/+siPiuZyRh9EfdaO0lqeDphjwdrOHws=; b=g jXkFvqlINg76d+o07hOk81d4tbA/YwFAB5BGUFmj41wQ2r1hKWoIC0ID9Y9oKUof wbhGt6xevtPK2LMMkFDLvoeE+nF4tfQAcmwU9fkPj1onaYrmQ6woGP+JTSZZvZ5h Itt28loq2sD6lur3POBzo2haZyAazKT7v/MawVwm9zLzuMwWpS5NTM1awf+bAZY9 BCLWF1L7EGJspxiyRVj0cTsh3UDxt/5vD4H2WrBtUji+R3Idq2ylUv+oVpGbc7KJ cxvhXN+xrlChj8oE9DfFYvses4F1FoYJAFB0PJUuShFBbBklaCRATb4VWgrHy6eC QcqTsLIRNJygOfsYZ4/Ug== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvddvtddgudehjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ekredttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdr khhlrghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeffleegie efgfevudehtdfhkeeutdffjeevgeffgeejvedthefgudeiteefheejheenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrg hvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 3 May 2024 17:06:39 -0400 (EDT) Message-ID: <32c6f80e-0531-4a30-a05c-c57bfa0d2d4c@aklaver.com> Date: Fri, 3 May 2024 14:06:38 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: David Gauthier , pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/3/24 13:58, David Gauthier wrote: > psql (15.3, server 14.5) on linux > > Someone else's DB which I've been asked to look at. > > \dt gives many tables, here are just 3... > >  public | some_idIds                                       | table | > cron_user >  public | WarningIds                                       | table | > cron_user >  public | cpf_inv_driverIds                                | table | > cron_user > > but \d public.some_idIds gives.. > > Did not find any relation named "public.some_idIds". > > Soooooo... what am I missing ? Try: select relname, length(relname) from pg_class where relname ilike '%some_idIds%'; Best guess there are hidden characters. > owner is "cron_user".  \dt shows cron_user is the owner of the table. > > -- Adrian Klaver adrian.klaver@aklaver.com From adrian.klaver@aklaver.com Fri May 15 23:22:53 2026 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 1s308x-008HWO-2m for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:08:34 +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 1s308u-00C5a6-DZ for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:08:33 +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 ) id 1s308u-00C5Zx-2R for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:08:32 +0000 Received: from wfout5-smtp.messagingengine.com ([64.147.123.148]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s308r-001Op8-Uz for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:08:32 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfout.west.internal (Postfix) with ESMTP id BC3941C00095; Fri, 3 May 2024 17:08:27 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Fri, 03 May 2024 17:08:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1714770507; x=1714856907; bh=gQw5prWwlJ+3TOUXbPfsbdOvrzLAEGYyFzam/jzzuoc=; b= G2A37QbpjwEcBW7JImE5BFVqZZ/rdkBU1RjvIxCAb4u+4+tW2rTz9oMIQqnf3Z1x SMX/QyhA0/el2wf2voEWFPOcK8pjVTWwYcR7dsEfF7hLuJNBk5vPZrGpvd1kDx4y 53AaXaCq77CHgIAhctQlqXUpfRH0EokkGFjYdyfAP3d54dmqmYNQqUWF+UpNhv5M bzu7lXDhtHumlGkKMbUryK6mQLZOSXe1s0j0p3w0+8igIjOMfIU9XIe8Zln1N+T4 MgvbZLB4Prj/B4favvZO5ErPxlodlnOlOxgLIyAq+aDkmzctt2GZWJ6LUpechDig 5RPRZsc4q5Nj6QOK97Kpwg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1714770507; x= 1714856907; bh=gQw5prWwlJ+3TOUXbPfsbdOvrzLAEGYyFzam/jzzuoc=; b=J H9KE0KKxlIUk+digoSDGuN4qS16CDmwAwhr/1VKr1MjiaSi05zFY9T20q+ntRAOF 5vMeCzhALPNXE9Yj2PlKjOOipN8eqg5YRpUS9/k4jX66kqPokN6eizGONIiT6xno X5Wq/fnrWCEHAel6qxd9tSxQZ2mQYojKmL79FS8D33dxtFTYXrPWRrSVnY/NvKY4 77trGF4cEQAMFssXipMeprWPg4/Fqnn333451ib0fR0wv3au0cP/igFvZTRdjjZJ VbOrcPNjdgEvBCgJe5NcFVMOFsb0eia5xmYHWgfKj/TNHlsT2MzZ5hBaauWnQPkE uS6+i9C2PujlxSF3r2CEg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvddvtddgudehjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthekredttddvjeenucfhrhhomheptegu rhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrd gtohhmqeenucggtffrrghtthgvrhhnpeejkeduteeuuddugeeukeegueehkeeuieetheeg ffekvdevgfethfelfedtueekgfenucffohhmrghinhepshhomhgvpghiughiughsrdhtoh dphhgrghgrnhguvghrrdhnvghtpdhrvgguphhilhhlqdhlihhnphhrohdrtghomhenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnh drkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 3 May 2024 17:08:26 -0400 (EDT) Message-ID: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> Date: Fri, 3 May 2024 14:08:26 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: Magnus Hagander , David Gauthier Cc: pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/3/24 14:06, Magnus Hagander wrote: > > > On Fri, May 3, 2024 at 10:58 PM David Gauthier > wrote: > > psql (15.3, server 14.5) on linux > > Someone else's DB which I've been asked to look at. > > \dt gives many tables, here are just 3... > >  public | some_idIds                                       | table > | cron_user >  public | WarningIds                                       | table > | cron_user >  public | cpf_inv_driverIds                                | table > | cron_user > > but \d public.some_idIds gives.. > > Did not find any relation named "public.some_idIds". > > > > Looks like you might need a \d "some_idIds" (include the quotes) since > it has an uppercase characters? This: "Did not find any relation named "public.some_idIds"." to me indicates it did look for the properly cased name. > > -- >  Magnus Hagander >  Me: https://www.hagander.net/ >  Work: https://www.redpill-linpro.com/ -- Adrian Klaver adrian.klaver@aklaver.com From magnus@hagander.net Fri May 15 23:23:36 2026 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 1s30Dl-008IJO-KV for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:13:33 +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 1s30Dj-00C9Xu-3H for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:13:31 +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 ) id 1s30Di-00C9Xm-Oi for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:13:31 +0000 Received: from mail-pg1-x534.google.com ([2607:f8b0:4864:20::534]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s30Dg-001Oz7-CO for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:13:30 +0000 Received: by mail-pg1-x534.google.com with SMTP id 41be03b00d2f7-61be599ab77so52235a12.1 for ; Fri, 03 May 2024 14:13:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander.net; s=mail; t=1714770806; x=1715375606; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=EzfBnA3T0aY+j9Jq5/gtbV8i10VDdetbaknTrsNRCtc=; b=LYNZtyf7SLJe0PQNc5EIdzSnJSYmNqOSppwY7RDFjnqi/gaD9+pgiROliOSPVwQCqL H91pPSjA4Lo27XeqtVRTe1fBa908fXF6K56dCMkcKLWs45BPFiTpMfMhllt2rq0qFf1R +DNgoWVEqLNsHgqujW1Ih71yyIiagy2z4rzBW0It++80s0ndv7xpekqxfFGuypBDN7Dp 5N0yKc5i8+PPc7BTShaLDCaChp9ntylyidytDTXcjZ2o9nrWMqWVuVhSCraawmME5N9T XsNSgrKkURWVQqLcNdqFEPFKGHJDtI7DAFOxYhIAz5KuzzS0dgGlS0TGKG57ASrqg8ra MD9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714770806; x=1715375606; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=EzfBnA3T0aY+j9Jq5/gtbV8i10VDdetbaknTrsNRCtc=; b=InD5Z1IDt4ovGfVmXuKyu5lWHicQxotBlL7rwYs/m7FMlmpd+oKpivz89QkVug9Fpl spn+3hy41mw1U/Q4umZkxoe4YGsP7IZv2xrCqdzsp9GK01tkXomMGDKS5ZmWcJg5Pz+k Mzz39Ca1x5Ku6Hx5gh1h3Ck80pFKQ9cnT4ePRy1lRz9YBOj0qtqmrTGb8FiQLdLqIiia HphTvlBPkMj+l/PvWIHEbkUwSgY1ij93G9ap/IF7ciBI7RghBDmgmO86MVOdKlyaMRqL FIHJ020oMRBNZgwwh3e1Cpe6ZdYR5PxNCx9Kjhb/A8xcxpLaJ2RBnj1unVkz09de9XUK mseQ== X-Forwarded-Encrypted: i=1; AJvYcCVvlO0RDLWExEDKZ5evBtG2DLJ14QFfC4cvC2EHSEWasKORqhD4qy6nCbj7CM91Sf/9Gc6RRV/2mhgIblzpEg5Aenow0c6Uo67fBmmnAfSVn+Hu X-Gm-Message-State: AOJu0YxyJGxfVl0+GegUrxHcJtuAX6C5jXXIGD9QLEabvU4NDYY6CpMA qvmgbDAqHTiFhaErHhsHiVPjrdBevcTFCVhufvGclonLRG1oysq9B5GCGhNiIEtM02ZpvR0cSIH 4RyzLiMIIchX0UyCQFdaHG1VwYkx0IStlTj+V X-Google-Smtp-Source: AGHT+IEKD1EPCrnaGrfB2lGnygKsAe3bjoUnQu0V+TLpPImuN7VLoTdqbkn1vy6XYxtsHYZ3X1u6C1Bfgv0AvgrF32g= X-Received: by 2002:a17:90b:90f:b0:2a6:c503:95f2 with SMTP id bo15-20020a17090b090f00b002a6c50395f2mr3820007pjb.16.1714770806158; Fri, 03 May 2024 14:13:26 -0700 (PDT) MIME-Version: 1.0 References: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> In-Reply-To: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> From: Magnus Hagander Date: Fri, 3 May 2024 23:13:14 +0200 Message-ID: Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: Adrian Klaver Cc: David Gauthier , pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000c5d561061793307d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c5d561061793307d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, May 3, 2024 at 11:08=E2=80=AFPM Adrian Klaver wrote: > On 5/3/24 14:06, Magnus Hagander wrote: > > > > > > On Fri, May 3, 2024 at 10:58=E2=80=AFPM David Gauthier > > wrote: > > > > psql (15.3, server 14.5) on linux > > > > Someone else's DB which I've been asked to look at. > > > > \dt gives many tables, here are just 3... > > > > public | some_idIds | table > > | cron_user > > public | WarningIds | table > > | cron_user > > public | cpf_inv_driverIds | table > > | cron_user > > > > but \d public.some_idIds gives.. > > > > Did not find any relation named "public.some_idIds". > > > > > > > > Looks like you might need a \d "some_idIds" (include the quotes) since > > it has an uppercase characters? > > This: > > "Did not find any relation named "public.some_idIds"." > > to me indicates it did look for the properly cased name. > That is arguably a really bad error message, because it puts those quotes there whether needed or not. if you put the quotes in there, you get: Did not find any relation named "public."some_idIds"". -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000c5d561061793307d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, May 3, 2024 at 11:08=E2=80=AF= PM Adrian Klaver <adrian.kl= aver@aklaver.com> wrote:
On 5/3/24 14:06, Magnus Hagander wrote:
>
>
> On Fri, May 3, 2024 at 10:58=E2=80=AFPM David Gauthier <dfgpostgres@gmail.com <= br> > <mailto:= dfgpostgres@gmail.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0psql (15.3, server 14.5) on linux
>
>=C2=A0 =C2=A0 =C2=A0Someone else's DB which I've been asked to = look at.
>
>=C2=A0 =C2=A0 =C2=A0\dt gives many tables, here are just 3...
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0public | some_idIds =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | table
>=C2=A0 =C2=A0 =C2=A0| cron_user
>=C2=A0 =C2=A0 =C2=A0 =C2=A0public | WarningIds =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | table
>=C2=A0 =C2=A0 =C2=A0| cron_user
>=C2=A0 =C2=A0 =C2=A0 =C2=A0public | cpf_inv_driverIds =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0| table
>=C2=A0 =C2=A0 =C2=A0| cron_user
>
>=C2=A0 =C2=A0 =C2=A0but \d public.some_idIds gives..
>
>=C2=A0 =C2=A0 =C2=A0Did not find any relation named "public.some_i= dIds".
>
>
>
> Looks like you might need a \d "some_idIds" (include the quo= tes) since
> it has an uppercase characters?

This:

"Did not find any relation named "public.some_idIds"."<= br>
to me indicates it did look for the properly cased name.

That is arguably a really bad error message, because it p= uts those quotes there whether needed or not. if you put the quotes in ther= e, you get:

Did not find any relation named "publi= c."some_idIds"".

--
=C2=A0Magnus= Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-linpro.com/
=
--000000000000c5d561061793307d-- From david.g.johnston@gmail.com Fri May 15 23:22:39 2026 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 1s30Eb-008ISC-5X for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:14:24 +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 1s30EY-00CCZM-Q9 for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:14:23 +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 1s30EY-00CCXB-FJ for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:14:23 +0000 Received: from mail-oo1-xc32.google.com ([2607:f8b0:4864:20::c32]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s30ES-001IfC-UF for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:14:22 +0000 Received: by mail-oo1-xc32.google.com with SMTP id 006d021491bc7-5b1ca71532bso74755eaf.0 for ; Fri, 03 May 2024 14:14:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714770856; x=1715375656; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=z7p8LnvkY3+ayJrCrMQv0OQiG5M+ozvYVroQJbbB3IQ=; b=aU3w485TvJkQGRlC3AN7yjqM9OZ0XORZlG6pIGS4NhosGiicO8/2h8IFJybxrfmBtz CagHMpB0cdpESp5Mo6aFWd1q4a+WNjPJrdjcAPOfFrz30UhiBgqsrOxheTxJNtdzUVqg PVh4YVv1UdUQqErv6DtuYIXEAy+6R9Ai+5mi27rFpKkpclwCVrh7TizwH1b9wDAra2vM 2HNAgwdQnYBkJeXBti21bkSqwHyK9OPYep+dzenyQJGKDorfcU8q+h1CGzP+FFCQhdqZ 4F5oVLVGr4zZYASXHP2jnGLPiAqVWgaYzAKXCMx/MfJCMIoOZ2y/liR11HljMN1ANRFp EztA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714770856; x=1715375656; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=z7p8LnvkY3+ayJrCrMQv0OQiG5M+ozvYVroQJbbB3IQ=; b=Mu0G4xUQey1iQMex0y9eHbxQDTNzRt2u/u+n5YekJjPzzXCxH1DMGC4kio48VQw1Sm cuKhf0ndCACoiAaqFKJL1BMeWl5C4xMiCXUKEG4o11KJ5zYSU30RTSySJR9zex0iSDxu HHzJR2ZGO28Knqk7kE3zuelk3KMLAcsCpPXh3hLRVT5XmPr1AjAxGHeJHG+U64xwwbXM 799PkzNkwoxBFgPuCoIXqZU4ccZH2q6bfjR7ddyNEDIX0AOd1d9paWztyKpWveeC1QMH 08g9mF+2kY207IYh6X/wnPL0NnBt8xeY1+hH10Mhf9/Jic4/m7mYxbY3RyMDVuPzz3II O/Ig== X-Forwarded-Encrypted: i=1; AJvYcCVEN16Dc2ZBSi++ABwfan4V0WsItd+2BMaX9sN/+PYEJeHqSuxMyGFApWOmelNQqFRwYp7xZJhl0hx5Mbfcw/rE6vbIpI1HX3qEwnVYpJM00hPh X-Gm-Message-State: AOJu0YxuR+wLF0yoIo/4dzO/aNLFhmOSDXGK30n2fh1Sy3zp/qnQNevQ fKIiDA5Rv/2SJqIEOlX1AZp4E04kLvy3q34pyfz9PpKFM/6jaWMSfDtdgoqHVtw25O5cZqhVpXt mSnoqIvsoamNuo7aLdBykwix8EpU= X-Google-Smtp-Source: AGHT+IEdq0pAUMCYzEKXEMzuMOEGZrQ1RppNazogTc/lQ2ld6jEoz5uV2jEJThAoZo0SAXc9C1EYiuveU2QJrE9iff4= X-Received: by 2002:a4a:304f:0:b0:5b1:d588:19 with SMTP id z15-20020a4a304f000000b005b1d5880019mr4025433ooz.4.1714770856113; Fri, 03 May 2024 14:14:16 -0700 (PDT) MIME-Version: 1.0 References: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> In-Reply-To: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> From: "David G. Johnston" Date: Fri, 3 May 2024 14:13:38 -0700 Message-ID: Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: Adrian Klaver Cc: Magnus Hagander , David Gauthier , pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000bffd4106179333b6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000bffd4106179333b6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, May 3, 2024 at 2:08=E2=80=AFPM Adrian Klaver wrote: > On 5/3/24 14:06, Magnus Hagander wrote: > > > > > > On Fri, May 3, 2024 at 10:58=E2=80=AFPM David Gauthier > > wrote: > > > > psql (15.3, server 14.5) on linux > > > > Someone else's DB which I've been asked to look at. > > > > \dt gives many tables, here are just 3... > > > > public | some_idIds | table > > > > > Looks like you might need a \d "some_idIds" (include the quotes) since > > it has an uppercase characters? > > This: > > "Did not find any relation named "public.some_idIds"." > > to me indicates it did look for the properly cased name. > > More likely there is confusion between an upper case I "eye" and a lower case l "el". David J. --000000000000bffd4106179333b6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, May 3, 2024 at 2:08=E2=80=AFPM Adrian Klaver <<= a href=3D"mailto:adrian.klaver@aklaver.com">adrian.klaver@aklaver.com&g= t; wrote:
On 5/3/24 14:06, Magnus Hagander wrote: >
>
> On Fri, May 3, 2024 at 10:58=E2=80=AFPM David Gauthier <dfgpostgres@gmail.com <= br> > <mailto:= dfgpostgres@gmail.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0psql (15.3, server 14.5) on linux
>
>=C2=A0 =C2=A0 =C2=A0Someone else's DB which I've been asked to = look at.
>
>=C2=A0 =C2=A0 =C2=A0\dt gives many tables, here are just 3...
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0public | some_idIds =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | table

>
> Looks like you might need a \d "some_idIds" (include the quo= tes) since
> it has an uppercase characters?

This:

"Did not find any relation named "public.some_idIds"."<= br>
to me indicates it did look for the properly cased name.


More likely there is confusion between an upper case I = "eye" and a lower case l "el".

Dav= id J.

--000000000000bffd4106179333b6-- From tgl@sss.pgh.pa.us Fri May 15 23:23:21 2026 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 1s30FZ-008IdM-8x for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:15:25 +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 1s30FW-00CFa3-OS for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:15:23 +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 ) id 1s30FW-00CFZs-E7 for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:15:23 +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 ) id 1s30FQ-001OzU-5x for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:15:22 +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 443LFBhe2746168; Fri, 3 May 2024 17:15:11 -0400 From: Tom Lane To: Adrian Klaver cc: 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: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> References: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> Comments: In-reply-to Adrian Klaver message dated "Fri, 03 May 2024 14:08:26 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2746166.1714770911.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 03 May 2024 17:15:11 -0400 Message-ID: <2746167.1714770911@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Adrian Klaver writes: > On 5/3/24 14:06, Magnus Hagander wrote: >> Looks like you might need a \d "some_idIds" (include the quotes) since = >> it has an uppercase characters? > This: > "Did not find any relation named "public.some_idIds"." > to me indicates it did look for the properly cased name. No, that message just regurgitates what you typed. Magnus is correct that the pattern will be case-folded if not quoted. You can check with --echo-hidden (-E): postgres=3D# \d public.some_idIds /******** QUERY *********/ SELECT c.oid, n.nspname, c.relname FROM pg_catalog.pg_class c LEFT JOIN pg_catalog.pg_namespace n ON n.oid =3D c.relnamespace WHERE c.relname OPERATOR(pg_catalog.~) '^(some_idids)$' COLLATE pg_catalog= .default AND n.nspname OPERATOR(pg_catalog.~) '^(public)$' COLLATE pg_catalog.def= ault ORDER BY 2, 3; /************************/ Did not find any relation named "public.some_idIds". So it is in fact looking for public.some_idids. regards, tom lane From tgl@sss.pgh.pa.us Fri May 15 23:22:36 2026 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 1s30SM-008Kea-Pj for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:28:38 +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 1s30SJ-00CNGo-TI for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 21:28:36 +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 ) id 1s30SJ-00CNGf-I8 for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:28:36 +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 ) id 1s30SH-001P5p-Tc for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 21:28:35 +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 443LSKpZ2747923; Fri, 3 May 2024 17:28:20 -0400 From: Tom Lane To: Magnus Hagander cc: Adrian Klaver , 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> Comments: In-reply-to Magnus Hagander message dated "Fri, 03 May 2024 23:13:14 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2747921.1714771700.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 03 May 2024 17:28:20 -0400 Message-ID: <2747922.1714771700@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Magnus Hagander writes: > On Fri, May 3, 2024 at 11:08 PM Adrian Klaver > wrote: >> This: >> "Did not find any relation named "public.some_idIds"." >> to me indicates it did look for the properly cased name. > That is arguably a really bad error message, because it puts those quotes > there whether needed or not. if you put the quotes in there, you get: > Did not find any relation named "public."some_idIds"". This is one of the places where it's unfortunate that our English-text rule for quoting a string to set it off from the rest of the error message collides with SQL's rule for quoting an identifier. Leaving out the outer quotes would be contrary to our style guide, but having them there can be confusing too to people who know SQL well. It'd be better if we could show the transformed search string, but since it's been marked up to be a regex I fear that'd introduce even more confusion than it solves. regards, tom lane From isaac.morland@gmail.com Fri May 15 23:21:57 2026 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 1s315D-008RQe-9e for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 22:08:47 +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 1s3158-00CYJR-BL for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 22:08:43 +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 ) id 1s3157-00CYJH-UD for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 22:08:42 +0000 Received: from mail-pj1-x102c.google.com ([2607:f8b0:4864:20::102c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s3156-001PKQ-9f for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 22:08:42 +0000 Received: by mail-pj1-x102c.google.com with SMTP id 98e67ed59e1d1-2a2da57ab3aso143113a91.3 for ; Fri, 03 May 2024 15:08:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714774118; x=1715378918; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=S+Y2Q+Ah2QH/BOZmZ7vSDMnNxjeuaEDgbpmUXimR3JE=; b=Btgoavocw4bLFcd1C1RE1NzpAgyGq0gxJ068uKv3ObMEtEb8nburBF/Ejw+9ozWWB3 9+yVhV9d03chVv7jyRqOz3PYK4PcpaTvqrXU0+qyYjRrswpGEo4kmNzR6WWnl1cpozHH eqehQ/jg+iCSXFrETXsvTnMuek7vUqhKiQvdHiIoYzeOcqsFWIbwuco8KREmu9wN083b lHUQOne4VE7LkktGn/TisaAN/daQ3xXc0ldjFduAJD4EPZ8VsawCEWp8xbYOJPSTwNXj fcvpUBtB/8oN89NMx4S+DXsitcoodRIYIC9Yct35Y8kQ/WJXGuLJOcdRuT1JqX1rBJKi 96bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714774118; x=1715378918; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=S+Y2Q+Ah2QH/BOZmZ7vSDMnNxjeuaEDgbpmUXimR3JE=; b=c2W+/5WPEzO9891WI1ZXaKzmqj3OnZ3kGP4ZWtJVqYMV8KElI6oLH0NQg/8j9XNx+n IRA/KHPV16M442TYXiZp7GlW3SlmNuF3v/hUionxdUmkhZiiv58br+JFq43M/vkHbFrV iAyZRL5pJFK/DZP22PRb3HjCNY6l13acEMalnca3GnnpRfpCYWxZX7LQifd8ijDBWb3Q Uk0kEMAX3q5ncuRsJNoAUHr6RjtElFWm9OyiWaNqS9qoFs4F/a0KPz2KcxG1WGma76Bp xRYl2DbfUB4ZX2Cx4aYYRfO8kjkV+wPMDVkWZPbEiPn8oB2QZZxxQl6T/MeUn8XNUMLq 8DDw== X-Forwarded-Encrypted: i=1; AJvYcCVxTOjkBXsVVGKjZ6F4PqQBZfUA63IkAspYxVrVqZFJnTlcNHMciwa32fZss0eMtWi5zx3xhmuVXQmJSGLTZy+8rFD52ozodAGtKfIgIBgIdKZA X-Gm-Message-State: AOJu0Yw5Rt+mR6a+9kErgoC2vwc1yW20vR0qyOvgENUcYd7oxpC5HMQz YZrBoPHemRUXS2EmDeq9VOVQH5HqO10irJcsQlPKDoz5dvrO4DurWCm2mSrkIjyFT3rVBxm5HrQ F/rvzbh7Q58hitdIlUht6yhKAWtg= X-Google-Smtp-Source: AGHT+IEnb1BHxnQxrJ40+GfVY9UZ7vglzkGwle+iqAnq6kEkl+qwLTS/fqP4hGGbGNiwETs70tvxWZXB+BP8r5LlQpk= X-Received: by 2002:a17:90b:3552:b0:2b2:926b:35e1 with SMTP id lt18-20020a17090b355200b002b2926b35e1mr3932016pjb.13.1714774118130; Fri, 03 May 2024 15:08:38 -0700 (PDT) MIME-Version: 1.0 References: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> <2747922.1714771700@sss.pgh.pa.us> In-Reply-To: <2747922.1714771700@sss.pgh.pa.us> From: Isaac Morland Date: Fri, 3 May 2024 18:08:25 -0400 Message-ID: Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: Tom Lane Cc: Magnus Hagander , Adrian Klaver , David Gauthier , pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000002e6f50061793f632" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002e6f50061793f632 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 3 May 2024 at 17:28, Tom Lane wrote: This is one of the places where it's unfortunate that our English-text > rule for quoting a string to set it off from the rest of the error > message collides with SQL's rule for quoting an identifier. Leaving > out the outer quotes would be contrary to our style guide, but having > them there can be confusing too to people who know SQL well. I'm not sure if this is a serious suggestion or not: enclose the name of the table, as you would type it in psql, between curly quotes. So for example: =E2=80=9Ctable_name=E2=80=9D =E2=80=9C"TableNameWithUpperCaseLetters"=E2=80=9D In a context where the curly quotes and surrounding message could be in a non-monospaced typeface and the table name (including double quote marks if needed) in a monospaced typeface this would be more natural. --0000000000002e6f50061793f632 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, 3 May 2024 at 17:28, Tom Lane <= ;tgl@sss.pgh.pa.us> wrote:
<= /div>

This is one of the places where it's unfortunate that our English-text<= br> rule for quoting a string to set it off from the rest of the error
message collides with SQL's rule for quoting an identifier.=C2=A0 Leavi= ng
out the outer quotes would be contrary to our style guide, but having
them there can be confusing too to people who know SQL well.

I'm not sure if this is a serious suggestion or not: = enclose the name of the table, as you would type it in psql, between curly = quotes.

So for example:

= =E2=80=9Ctable_name=E2=80=9D
=E2=80=9C"TableNameWithUpperCas= eLetters"=E2=80=9D

In a context where the cur= ly quotes and surrounding message could be in a non-monospaced typeface and= the table name (including double quote marks if needed) in a monospaced ty= peface this would be more natural.

--0000000000002e6f50061793f632-- From jian.universality@gmail.com Fri May 15 23:22:34 2026 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 1s36Gz-009Qde-27 for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 03:41:16 +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 1s36Gv-00EenW-2L for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 03:41:13 +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 ) id 1s36Gu-00EenH-Ll for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 03:41:13 +0000 Received: from mail-vk1-xa2e.google.com ([2607:f8b0:4864:20::a2e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s36Gt-001RbX-2w for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 03:41:12 +0000 Received: by mail-vk1-xa2e.google.com with SMTP id 71dfb90a1353d-4dac112e192so133198e0c.1 for ; Fri, 03 May 2024 20:41:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714794069; x=1715398869; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=nvShUV/95vkYoTcGPVoF/KipW8t/7jOnVNY5wDwaGD8=; b=biv/n8+eFhQRSQBxMD93zcas4cPbjLpsbuWfgcq4TTR4/T8VQlkuoP4PYUbz9T0z9B Kas2fV2AryE5znH96bTv8UNcH4mSNRlb+CquPG/pYOlsVT+22giaWJ/zSroS4VTv7pa8 oixrwcof0XC+kyiz4ugt/jeG2NTp3d5+z1+X7x0Bo3/ewlv05LCnn5YyhXSYyT9cZ95t xOUxf1lRjAZFhh8YJZnvuATqkR6YL7UxW/aiWyx7ZtYJ3sy26EaJ9LKzexThOKman7HZ bKB80Km/o1N619ctdltcZ2A3JRD//VrvfOJbeYZ1sqGkJi140w1zvKY3qyNxTX8ExAET 9dyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714794069; x=1715398869; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=nvShUV/95vkYoTcGPVoF/KipW8t/7jOnVNY5wDwaGD8=; b=JrCcwxIEbxJGCuFJLN+XLW86JfTyVVHArl3gKEf/+4PAbg4+tqmny71phK0/Dh0Dca YfLb3svFCxxRHezv+afWBNZ9t7WiJyxOvWcMOm6cW2zesEXQG0oyzoPC1x7/FGK2o6X+ a7Un1o4HAyb+y0thLBG+9FXh94B/B5hJphfZcMh8r4Udp9gEs4SNcInXPrw/G3R8y8pV B9cAwkOtZe8lpTWvTnjQLu/ewpVTX+pDJ6KAFohw4KjOH2N0SmTe7yNa2WXhmVYgDZU5 JJ7AbD8ARN9W5CelyW+2v3mNwsODEwd8bLkWtowKwVzk5UdufoKrs2HzXWwh2moaFs9z zkPA== X-Forwarded-Encrypted: i=1; AJvYcCWiXppfr611qSEfiAxkzdYg/X9vZ2Nt3g+sxusF2WRJs/3+qusywkkYV3pCU1eUpIE1QriPzNbRYKC+T6G3lSBwNRLIunSaf1A9Hz2xjo5aeFmm X-Gm-Message-State: AOJu0Ywx/Aix0ib+asAU9Joz0LWeJSQRL32Ua0vU4/Khkarpmy55OIQ9 IKqirhF56Vr2uV+Hr6NaVjA6y3UkoOwYL1mVEipKoXEcc2M1lf0um2N1zLzkUyuzNIv5L9szzy1 +4YdcKsFVMHpM8GEqcAmSEOWJv6U= X-Google-Smtp-Source: AGHT+IFQm2hPE82XsgMexELfNYNUWkahIb/+Oirg4L/cmX5Nm8BMoqyftTFHGqs99+JXjiWzrnqUSVR51+V4gL0dD64= X-Received: by 2002:a05:6122:99f:b0:4da:a531:ba26 with SMTP id g31-20020a056122099f00b004daa531ba26mr4958047vkd.6.1714794067771; Fri, 03 May 2024 20:41:07 -0700 (PDT) MIME-Version: 1.0 References: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> <2746167.1714770911@sss.pgh.pa.us> In-Reply-To: <2746167.1714770911@sss.pgh.pa.us> From: jian he Date: Sat, 4 May 2024 11:40:56 +0800 Message-ID: Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: Tom Lane Cc: Adrian Klaver , Magnus Hagander , David Gauthier , pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, May 4, 2024 at 5:15=E2=80=AFAM Tom Lane wrote: > > Adrian Klaver writes: > > On 5/3/24 14:06, Magnus Hagander wrote: > >> Looks like you might need a \d "some_idIds" (include the quotes) since > >> it has an uppercase characters? > > > This: > > "Did not find any relation named "public.some_idIds"." > > to me indicates it did look for the properly cased name. > > No, that message just regurgitates what you typed. Magnus is > correct that the pattern will be case-folded if not quoted. > You can check with --echo-hidden (-E): > > postgres=3D# \d public.some_idIds > /******** QUERY *********/ > SELECT c.oid, > n.nspname, > c.relname > FROM pg_catalog.pg_class c > LEFT JOIN pg_catalog.pg_namespace n ON n.oid =3D c.relnamespace > WHERE c.relname OPERATOR(pg_catalog.~) '^(some_idids)$' COLLATE pg_catalo= g.default > AND n.nspname OPERATOR(pg_catalog.~) '^(public)$' COLLATE pg_catalog.de= fault > ORDER BY 2, 3; > /************************/ > > Did not find any relation named "public.some_idIds". > > So it is in fact looking for public.some_idids. > make it case insensitive? like > WHERE c.relname OPERATOR(pg_catalog.~*) '^(some_idids)$' COLLATE pg_catal= og.default we already transformed `\d SOME_IDIDS` to `\d some_idids`, in some way it looks case-insensitive. From tgl@sss.pgh.pa.us Fri May 15 23:22:23 2026 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 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 ) 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 ) 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 ) 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 To: jian he cc: 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> Comments: In-reply-to jian he 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: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk jian he 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 From david.g.johnston@gmail.com Fri May 15 23:21:59 2026 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 1s36fL-009UcN-Hv for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:06:27 +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 1s36fI-00Er4W-Mc for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:06:25 +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 1s36fI-00Er0w-5P for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:06:25 +0000 Received: from mail-ot1-x32a.google.com ([2607:f8b0:4864:20::32a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s36fG-001LMZ-2s for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:06:23 +0000 Received: by mail-ot1-x32a.google.com with SMTP id 46e09a7af769-6ee2be5b765so169969a34.0 for ; Fri, 03 May 2024 21:06:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714795581; x=1715400381; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=SmwTLGtEnYYcy1TWUESHX4pIi2U9SlHEwHzmNIASgtI=; b=Kt0G0Fr7BKz1zRp9/x5xCoFfntyBzbOMcCBLOFS2He28bNydLdjt9/2qz/4fxyxIOO 3D57ROuGloZv4wdu2TllUx0rnIpiOVkjfS/tibDn1FS6Ba2frQiFTQlAcP9rfxNpKovL MebUYhDd45LTVaea02H0Xq6d4exPkrz4chN7z8i2sQtDbDKFS9bJvf9zD+iby1kF02f+ f+kPDrmjQuztOIoBX+T8fEYK0y4FZMCEYp83llz25/80GMfWKXZSJaZBLvL2dkvqIwe5 UL/Bh9ZTBz2NvEHbcwwmrQ9MDFinYR2txdz7tRH5l0HS6VC0AYRwO0sgH9Q9pep4Hwss x8hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714795581; x=1715400381; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=SmwTLGtEnYYcy1TWUESHX4pIi2U9SlHEwHzmNIASgtI=; b=Gydst4qVm/ex/4Fse7H4C04rRnXoBwakvn2MqdSsXdQjq6O9KU5PfI96XKqhkhHUJ+ ieMGqIvuK1IrnvHJ3O7bxezYzuAgfPuBz3JiSvq6KgWY/0QprHu3YrYWa57DmCEyD7f5 TfB40WJnG5cZqIXtuFBxeGG3edWFRDlHNdKcB8quJTwmSgCzUdPCpnZfsi7TvXMdmpb1 BTQhTIXrooF4Q/u30bQVv9MwqFXaA7q38XgW6hbpXG8pty/S427CdfhojNU0kbQ6KFaR b+FjWX4W/ACWP0mnlpUUKxQyOu1DuCaZ4Jx7Ewa3qQbUySNdI9wpBHBp1VIIptqriqwh L38Q== X-Forwarded-Encrypted: i=1; AJvYcCUO0z0xS/r6Uv//9f+IHhOzMyPgs81Z+NiiTweMdfBlvsyOExAZK856sLwFI8ngIXt3sgXsNuVKwXKw8s6MpY2AIfRP+uH/SS66Ekwh8USxTAeO X-Gm-Message-State: AOJu0YxoEhFJkRqbqLprTjXmPNLPze+BCzZxu4/w4lhXVXZ8U2EMohhU YAVEsD9ImaKlzcy0OTdtgi8HL2KB45aCCKtIaMHM9BNuaD8motsNhmd1Ng6Qd8ZOgjGrGhxmasq tzLKkjbtfxxLxxkbDlnqUKuRodxQ= X-Google-Smtp-Source: AGHT+IFX37IYKeHpiS2NnDOTqi+J+rsply2NiWyewhF4Ky0OzPGblhrwOhICfqZSztpXJHgbQnhNZ02vJ2b2tVWL63E= X-Received: by 2002:a9d:6b84:0:b0:6eb:7edd:c2fa with SMTP id b4-20020a9d6b84000000b006eb7eddc2famr4895737otq.4.1714795580657; Fri, 03 May 2024 21:06:20 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:5f0a:0:b0:52a:9016:8503 with HTTP; Fri, 3 May 2024 21:06:20 -0700 (PDT) In-Reply-To: <2808875.1714794677@sss.pgh.pa.us> References: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> <2746167.1714770911@sss.pgh.pa.us> <2808875.1714794677@sss.pgh.pa.us> From: "David G. Johnston" Date: Fri, 3 May 2024 21:06:20 -0700 Message-ID: Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: Tom Lane Cc: jian he , Adrian Klaver , Magnus Hagander , David Gauthier , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000007296c1061798f5ae" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007296c1061798f5ae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 their DB because their client language preserves case and doesn=E2=80=99t require= quoting. And it isn=E2=80=99t like any sane person is using case to distinguish name= s in their DB and so would be at risk of seeing multiple unwanted matches for any given pattern. I don=E2=80=99t think name pattern matching during object lookup is a good = tool to wield to try and convince people that using camel case is a bad idea and they should use snake case instead. If they don=E2=80=99t write enough raw= SQL to be annoyed by their choice more power to them, making \d more accessible for them is a win and snake case people won=E2=80=99t notice or care. David J. --0000000000007296c1061798f5ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, May 3, 2024, Tom Lane <t= gl@sss.pgh.pa.us> 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.=C2=A0 I don't see why it's a surprise that that= is also
true in \d commands.


Every day the number of people increases w= ho get mixed-case names in their DB because their client language preserves= case and doesn=E2=80=99t require quoting.

And it = isn=E2=80=99t like any sane person is using case to distinguish names in th= eir DB and so would be at risk of seeing multiple unwanted matches for any = given pattern.

I don=E2=80=99t think name pattern = matching during object lookup is a good tool to wield to try and convince p= eople that using camel case is a bad idea and they should use snake case in= stead.=C2=A0 If they don=E2=80=99t write enough raw SQL to be annoyed by th= eir choice more power to them, making \d more accessible for them is a win = and snake case people won=E2=80=99t notice or care.

David J. --0000000000007296c1061798f5ae-- From tgl@sss.pgh.pa.us Fri May 15 23:22:17 2026 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 From adrian.klaver@aklaver.com Fri May 15 23:23:03 2026 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 1s36vY-009XFo-8I for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:23:12 +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 1s36vV-00F1H3-Lz for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:23:10 +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 ) id 1s36vT-00F1Gu-R5 for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:23:10 +0000 Received: from fout1-smtp.messagingengine.com ([103.168.172.144]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s36vL-001Rtm-Sa for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:23:07 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfout.nyi.internal (Postfix) with ESMTP id 6D1A51380356; Sat, 4 May 2024 00:22:57 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sat, 04 May 2024 00:22:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1714796577; x=1714882977; bh=kbhfU2ZSS4C6bzMZrSljR+XR63PXj6UML14KcK7WBJo=; b= K9F6O+tD5QrQovZ0YLmnrYjJnRkDxYgLjkFCRioy7NflvTEN0BXxFcNI3maUQ7yX aIkVQMm9MLUxJGt0GyDEtUZeQGFZdlOvIO1L9F7dWkVqy13BaQu4b70tGXRLfAb6 vFXnMXUnq4fQOHk36osK+d/K0LSS/mj88lE/jMiO4ihoSjkFrRHsoMbBEG4c61LT 8d7QIjIjibeCA52Go32vjdQcy/+2BqxkkFZ8vU2G3oCPW0VIGguLfX8qMbLgrMB6 q8t/Re+UKaQcvOvF0bilwhI4wTPQtgtNv0AiqmZMNKpJ9pMHe6tq1c2JuTuW2Ty6 PiTEn67BO08XiM0OOzvgpg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1714796577; x= 1714882977; bh=kbhfU2ZSS4C6bzMZrSljR+XR63PXj6UML14KcK7WBJo=; b=k nsC0oxaAvgWEWggdmAlD6tZy+su66MG7Txc9V4CdGo0FPboflG+nqmyXWPuh1aBK osEFbGDGMxQrWXzDYqPfrGFU5P/IcZ7BDEl7L2j4XOUAdBwXKqYdOAjaB3pxbqOe 7jEhVdLOuGe1NSH8O4KTFE73/yvavoQ2lvpCRbXsIA5F38oIaV9CL1bRhLN9j9He 2PS9MA2G0cpI3l5+ftzCgnhK16Foy95QZwFvRk6DKcp/IQbBze4BjAue8szGnSmD OWyLevv5mV2LSDkW+JHyMk2DzF7X86NclRY2++GI6mZCD3U0I02F7IisbXWOVi4M f91tMuTbW8Kuuu4YoQHXw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvddvuddgjeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepgfdufeekhfevfeelveeiueevhedvuddukeduvddv lefhueeuieejtdeuvdevvdeunecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughr ihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 4 May 2024 00:22:56 -0400 (EDT) Message-ID: <8a888f00-3752-463e-87c6-bb3979c7a4b8@aklaver.com> Date: Fri, 3 May 2024 21:22:55 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: "David G. Johnston" , Tom Lane Cc: jian he , Magnus Hagander , David Gauthier , "pgsql-general@lists.postgresql.org" References: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> <2746167.1714770911@sss.pgh.pa.us> <2808875.1714794677@sss.pgh.pa.us> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/3/24 21:06, David G. Johnston wrote: > 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 > their DB because their client language preserves case and doesn’t > require quoting. In a sense they do by making quoting the default, which people find out when they stray from the language/ORM/framework and get pointed at: https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS > > And it isn’t like any sane person is using case to distinguish names in > their DB and so would be at risk of seeing multiple unwanted matches for > any given pattern. Have you met people? > > I don’t think name pattern matching during object lookup is a good tool > to wield to try and convince people that using camel case is a bad idea > and they should use snake case instead.  If they don’t write enough raw > SQL to be annoyed by their choice more power to them, making \d more > accessible for them is a win and snake case people won’t notice or care. > > David J. -- Adrian Klaver adrian.klaver@aklaver.com From david.g.johnston@gmail.com Fri May 15 23:23:39 2026 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 1s37J5-009akY-KC for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:47:31 +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 1s37J0-00FAYw-It for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:47:27 +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 1s37J0-00FAYn-5Y for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:47:27 +0000 Received: from mail-ot1-x32f.google.com ([2607:f8b0:4864:20::32f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s37Iy-001LdM-F2 for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:47:25 +0000 Received: by mail-ot1-x32f.google.com with SMTP id 46e09a7af769-6eb8ea5ac95so180963a34.2 for ; Fri, 03 May 2024 21:47:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714798044; x=1715402844; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=glBPEwOlZPw+Fdc94oAc34vs6JGxDcAxrAriYF6uyEA=; b=nWrHsI5VQOdDdYQonZhOWsdzP8j9otdLlXx3UerN1cBOWNyWveJ19V7ok5fqj1s+o4 BtFZfQJEfylocttjosR5vQeBwU3RJQ8RI2PlOcH0pAJG+wMwZbiPnz7PU3Fq9QtKPT1S PUWpcju3azQo2FJtbvTnLsQS17QLlX2icQciy2DHBlaPEHjaFLo0OXCKlpZzArXDUtNY A9taJR3Exq1mlA8sOIG9dwpd/kYxuTRdBbRTbi13ogEwbDXFJfZDNOUMMakBA2HdsTBX jW+tz9KVpjO0D+SOF0ydRzDZ5vH0pZJWRmNTUIsKz+jft/l9al6ns/fNxTT7bqrVM91D 1Axg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714798044; x=1715402844; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=glBPEwOlZPw+Fdc94oAc34vs6JGxDcAxrAriYF6uyEA=; b=Ja4ahZLSpWS5jYlFyva0HgVOj7aArqiaqGz4iQf5ThzWO5ZAf2SyZg4U+ie6U0qp3l yINKoj0F5EoHr4Hv/TXDdWADZXqJY/QQa54VqFFPSW2t/VqDTkUKgOTtLz43INqpeJmk MPSToJTa5k2eZdrYy9JRMv8i1Oa0gA2bsHz39J7Z2wFennLdVjaGWXNhqFoTCGEAaYHq pfi1rbli/17AfiJq01B1xyNUtts24yvHcxRHf2Oe9wc5owAujl7L1azw5H48w95j5JT/ Wrbmyz6vjOGCRvm79Rtwc6gck+RVmI/fHRqOm6H23066Dd1mQb2I3+bIvoxNuTroUaHu yHrQ== X-Forwarded-Encrypted: i=1; AJvYcCU5l56Fzv97t6sFw/Asmdt1kDF0ikUT8+sk6y9x3P4CcE19u8DK3kjlxhmKVFySB316dx9b5/df4fgNVyEKQqxX4h4LK7k4iW0jpRLQeMhQEdhj X-Gm-Message-State: AOJu0YzrLaWLM4SNLugchmV7ANkJ6qdBMskpWt1YpePaWm3+qa8Yig7M DEqhp2Pnh03BH5j2KRphGMSIyfnrf15sj29SEVNoJL0CAqvLOEyNg2HD/ku4UiXfb8Dm54uVjwb nruceGv6dEdy3MdKnV8+C0k+ZtzI= X-Google-Smtp-Source: AGHT+IFzUfKthrCSE4pQEJriyvLBfWgKlNKuOhIEjTUbLQP7syZs0negX8y/08SAK4AJAQTqHpIB2nd0UpKpyeTDgWk= X-Received: by 2002:a9d:7d98:0:b0:6eb:79fe:893 with SMTP id j24-20020a9d7d98000000b006eb79fe0893mr5567723otn.2.1714798043768; Fri, 03 May 2024 21:47:23 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:5f0a:0:b0:52a:9016:8503 with HTTP; Fri, 3 May 2024 21:47:23 -0700 (PDT) In-Reply-To: <8a888f00-3752-463e-87c6-bb3979c7a4b8@aklaver.com> References: <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> <2746167.1714770911@sss.pgh.pa.us> <2808875.1714794677@sss.pgh.pa.us> <8a888f00-3752-463e-87c6-bb3979c7a4b8@aklaver.com> From: "David G. Johnston" Date: Fri, 3 May 2024 21:47:23 -0700 Message-ID: Subject: Re: \dt shows table but \d
says the table doesn't exist ? To: Adrian Klaver Cc: Tom Lane , jian he , Magnus Hagander , David Gauthier , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000042b0740617998808" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000042b0740617998808 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, May 3, 2024, Adrian Klaver wrote: > > Have you met people? > I really don=E2=80=99t care enough to try and actually make converts here. = It would have been a perfectly justifiable design choice to make our =E2=80=9C= pattern=E2=80=9D matching case-insensitive by default, probably with a case-sensitive mode and no need to hack up quoting rules that are unique to it. It=E2=80=99s a= find feature and search benefits from case-insensitivity. There isn=E2=80=99t a= nything so compelling about the current behavior that it seems like the superior choice. But maybe you are right and I just lack sufficient real-world experience to see things differently. I also get not wanting to change behavior at this point though I=E2=80=99d = welcome a modifier like =E2=80=9C*=E2=80=9D (like the ~* operator) to enable case-i= nsensitive matching. David J. --00000000000042b0740617998808 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, May 3, 2024, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

Have you met people?

I really don=E2=80=99t care enough to try = and actually make converts here.=C2=A0 It would have been a perfectly justi= fiable design choice to make our =E2=80=9Cpattern=E2=80=9D matching case-in= sensitive by default, probably with a case-sensitive mode and no need to ha= ck up quoting rules that are unique to it.=C2=A0 It=E2=80=99s a find featur= e and search benefits from case-insensitivity.=C2=A0 There isn=E2=80=99t an= ything so compelling about the current behavior that it seems like the supe= rior choice.=C2=A0 But maybe you are right and I just lack sufficient real-= world experience to see things differently.

I also= get not wanting to change behavior at this point though I=E2=80=99d welcom= e a modifier like =E2=80=9C*=E2=80=9D (like the ~* operator) to enable case= -insensitive matching.

David J.

--00000000000042b0740617998808-- From tgl@sss.pgh.pa.us Fri May 15 23:22:23 2026 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 1s37TL-009cLs-CX for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:58:07 +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 1s37TI-00FGoz-Du for pgsql-general@arkaria.postgresql.org; Sat, 04 May 2024 04:58:05 +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 1s37TI-00FGoq-3D for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:58:04 +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 1s37TC-001LhX-O1 for pgsql-general@lists.postgresql.org; Sat, 04 May 2024 04:58:03 +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 4444vtaS2826786; Sat, 4 May 2024 00:57:55 -0400 From: Tom Lane To: "David G. Johnston" cc: Adrian Klaver , jian he , 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> <8a888f00-3752-463e-87c6-bb3979c7a4b8@aklaver.com> Comments: In-reply-to "David G. Johnston" message dated "Fri, 03 May 2024 21:47:23 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2826784.1714798675.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Sat, 04 May 2024 00:57:55 -0400 Message-ID: <2826785.1714798675@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > ... I’d welcome > a modifier like “*” (like the ~* operator) to enable case-insensitive > matching. We could talk about that idea, certainly. I'm afraid it's the sort of edge case that would mainly be useful to newbies who haven't read the docs closely enough to know the option exists, let alone that it will help them. But maybe there's more use-case than I'm thinking of. regards, tom lane From depesz@depesz.com Fri May 15 23:22:26 2026 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 1s3XIt-00Dj9U-Dl for pgsql-general@arkaria.postgresql.org; Sun, 05 May 2024 08:33:03 +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 1s3XIp-005tWu-Uq for pgsql-general@arkaria.postgresql.org; Sun, 05 May 2024 08:33: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.94.2) (envelope-from ) id 1s3XIp-005tWm-Hq for pgsql-general@lists.postgresql.org; Sun, 05 May 2024 08:33:00 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s3XIj-001e4e-GH for pgsql-general@lists.postgresql.org; Sun, 05 May 2024 08:32:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To: Message-ID:Subject:Cc:To:Sender:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description; bh=6HPf/1eBlhnYgJHEKh0t+HZ66FxL4fB1bzNKUMb2OfM=; b=KfU9iUC48RVgflwh7/fIBvKfTX FAvLCS18CwOqn87dOH1/kUYcfqQwPQPkH5MaJklcjgV7HKFQBpvA/xF5Tsl0qz/jTq2qEP2tQV1dC FTFNl/64b06IgnLCMfbFHIeacHjnMASp9A8U+qBRSIrZH0YLMrmpi/mZDlk/qcm/ocBA=; Received: from depesz by depesz.com with local (Exim 4.96) (envelope-from ) id 1s3XIi-00GJXu-0T; Sun, 05 May 2024 10:32:52 +0200 Date: Sun, 5 May 2024 10:32:52 +0200 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: David Gauthier Cc: pgsql-general@lists.postgresql.org Subject: Re: \dt shows table but \d
says the table doesn't exist ? Message-ID: Reply-To: depesz@depesz.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, May 03, 2024 at 04:58:26PM -0400, David Gauthier wrote: > Soooooo... what am I missing ? > owner is "cron_user". \dt shows cron_user is the owner of the table. Magnus already helped you, but you might want to check this: https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_upper_case_table_or_column_names and generally read the whole "Don't Do This" wiki page. Best regards, depesz