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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg14 psql broke \d datname.nspname.relname
Date: 2021-11-05 13:59:42
Message-ID: 413526.1636120782@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I think it would appropriate to normalize identifiers that are going to
> be stored in catalogs. As presented, this is a bit ridiculous and I see
> no reason to continue to support it.

If we had any sort of convention about the encoding of identifiers stored
in shared catalogs, maybe we could do something about that. But we don't,
so any change is inevitably going to break someone's use-case.

In any case, that seems quite orthogonal to the question of how to treat
names with too many dots in them. Considering we are three days out from
freezing 14.1, I think it is time to stop the meandering discussion and
fix it. And by "fix", I mean revert to the pre-14 behavior.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-11-05 14:04:26 Re: remove internal support in pgcrypto?
Previous Message Alvaro Herrera 2021-11-05 13:49:44 Re: removing global variable ThisTimeLineID