Re: pg14 psql broke \d datname.nspname.relname - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg14 psql broke \d datname.nspname.relname
Date
Msg-id 523498.1633989841@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg14 psql broke \d datname.nspname.relname  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: pg14 psql broke \d datname.nspname.relname  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
Mark Dilger <mark.dilger@enterprisedb.com> writes:
> I can only assume that you are intentionally misspelling "regression" as "regresion" (with only one "s") as part of
thetest.  I have not checked if that worked before v14, but if it ignored the misspelled database name before v14, and
itrejects it now, I'm not sure that counts as a bug.  

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".

            regards, tom lane



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: pg14 psql broke \d datname.nspname.relname
Next
From: Mark Dilger
Date:
Subject: Re: pg14 psql broke \d datname.nspname.relname