Duplicate tables information through metadata queries - Mailing list pgsql-jdbc

From David G. Johnston
Subject Duplicate tables information through metadata queries
Date
Msg-id CAKFQuwYp4ZZ9-FRCYhtwPptrxSJFxc-o=NU_r80tGp-uyct1zw@mail.gmail.com
Whole thread Raw
In response to Re: Duplicate tables information through metadata queries  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Duplicate tables information through metadata queries  (Dave Cramer <davecramer@postgres.rocks>)
List pgsql-jdbc
On Wednesday, September 8, 2021, Andrew Dunstan <andrew@dunslane.net> wrote:

On 9/8/21 5:15 PM, ldh@laurent-hasson.com wrote:
>
> SELECT *
> FROM pg_catalog.pg_class c
>      LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
>      LEFT JOIN pg_catalog.pg_description d ON (c.oid = d.objoid AND d.objsubid = 0)
> WHERE c.relname = 'contact'



Umm, that doesn't look right. For queries against pg_description you
need to specify the classoid (in this case 'pg_class'::regclass) as well
as the objoid (and possibly the objsubid). Remember, Oids are not unique
across the whole catalog. I looks to me like here one rwo is picking up
a description for an entry in some other catalog


See https://www.postgresql.org/docs/devel/catalog-pg-description.html


Doh!  I knew I was forgetting something.  This is indeed a bug in the JDBC driver.  In the query results a few messages above one is in catalog 1255 and the other (correct one) is in 1259.

David J.

pgsql-jdbc by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Duplicate tables information through metadata queries
Next
From: Dave Cramer
Date:
Subject: Re: Duplicate tables information through metadata queries