> On Oct 11, 2021, at 3:04 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Doesn't work with the correct DB name, either:
>
> regression=# \d public.bit_defaults
> Table "public.bit_defaults"
> Column | Type | Collation | Nullable | Default
> --------+----------------+-----------+----------+---------------------
> b1 | bit(4) | | | '1001'::"bit"
> b2 | bit(4) | | | '0101'::"bit"
> b3 | bit varying(5) | | | '1001'::bit varying
> b4 | bit varying(5) | | | '0101'::"bit"
>
> regression=# \d regression.public.bit_defaults
> Did not find any relation named "regression.public.bit_defaults".
REL_13_STABLE appears to accept any amount of nonsense you like:
foo=# \d nonesuch.foo.a.b.c.d.bar.baz
Table "bar.baz"
Column | Type | Collation | Nullable | Default
--------+---------+-----------+----------+---------
i | integer | | |
Is this something we're intentionally supporting? There is no regression test covering this, else we'd have seen
breakagein the build-farm.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company