Horton

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

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Greg Stark <stark@mit.edu>, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, Julien Rouhaud <rjuju123@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Justin Pryzby <pryzby@telsasoft.com>, Stephen Frost <sfrost@snowman.net>, Peter Geoghegan <pg@bowt.ie>
Date: 2022-04-20T15:54:52Z
Lists: pgsql-hackers 
On Tue, Apr 19, 2022 at 10:20 PM Mark Dilger
<mark.dilger@enterprisedb.com> wrote:
> Looks like most people voted for (B).  In support of that option, here are patches for master and REL_14_STABLE.  Note that I extended the tests compared to v9, which found a problem that is fixed for v10:

OK, I committed these. I am not totally sure we've got all the
problems sorted here, but I don't think that continuing to not commit
anything is going to be better, so here we go.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

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.