Re: pg14 psql broke \d datname.nspname.relname

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org
Date: 2021-10-11T22:04:01Z
Lists: 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 the test.  I have not checked if that worked before v14, but if it ignored the misspelled database name before v14, and it rejects 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



Commits

  1. Remove some recently-added pg_dump test cases.

  2. Allow db.schema.table patterns, but complain about random garbage.

  3. Improve error handling of HMAC computations

  4. Factor pattern-construction logic out of processSQLNamePattern.