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

From Peter Geoghegan
Subject Re: pg14 psql broke \d datname.nspname.relname
Date
Msg-id CAH2-Wz=S9OL4nwppApn2F4HVQDDUjzow8HhZfCMU3+Uyt-u7mA@mail.gmail.com
Whole thread Raw
In response to Re: pg14 psql broke \d datname.nspname.relname  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: pg14 psql broke \d datname.nspname.relname
List pgsql-hackers
On Mon, Oct 11, 2021 at 7:09 PM Mark Dilger
<mark.dilger@enterprisedb.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



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: BUG #17212: pg_amcheck fails on checking temporary relations
Next
From: Ajin Cherian
Date:
Subject: Re: row filtering for logical replication