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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg14 psql broke \d datname.nspname.relname
Date: 2021-10-12 02:33:10
Message-ID: CAH2-Wz=S9OL4nwppApn2F4HVQDDUjzow8HhZfCMU3+Uyt-u7mA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 11, 2021 at 7:09 PM Mark Dilger
<mark(dot)dilger(at)enterprisedb(dot)com> wrote:
> I was just wondering when it might be time to stop being lenient in psql and instead reject malformed identifiers.

I suppose that I probably wouldn't have chosen this behavior in a
green field situation. But Hyrum's law tells us that there are bound
to be some number of users relying on it. I don't think that it's
worth inconveniencing those people without getting a clear benefit in
return.

Being lenient here just doesn't have much downside in practice, as
evidenced by the total lack of complaints about that lenience.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ajin Cherian 2021-10-12 02:33:12 Re: row filtering for logical replication
Previous Message Mark Dilger 2021-10-12 02:22:14 Re: BUG #17212: pg_amcheck fails on checking temporary relations