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

From Mark Dilger
Subject Re: pg14 psql broke \d datname.nspname.relname
Date
Msg-id 6B0A82E1-CE3F-4AFE-8A1D-D1FA1862174C@enterprisedb.com
Whole thread Raw
In response to pg14 psql broke \d datname.nspname.relname  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers

> On Oct 11, 2021, at 3:26 PM, Justin Pryzby <pryzby@telsasoft.com> wrote:
>
> It looks like before v13 any "datname" prefix was ignored.

The evidence so far suggests that something is broken in v14, but it is less clear to me what the appropriate behavior
is. The v14 psql is rejecting even a correctly named database.schema.table, but v13 psql accepted
lots.of.nonsense.schema.table,and neither of those seems at first glance to be correct.  But perhaps there are good
reasonsfor ignoring the nonsense prefixes? 

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company






pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: pg14 psql broke \d datname.nspname.relname
Next
From: Tom Lane
Date:
Subject: Re: pg14 psql broke \d datname.nspname.relname