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

From Justin Pryzby
Subject Re: pg14 psql broke \d datname.nspname.relname
Date
Msg-id 20211012165745.GM27491@telsasoft.com
Whole thread Raw
In response to Re: pg14 psql broke \d datname.nspname.relname  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pg14 psql broke \d datname.nspname.relname
Re: pg14 psql broke \d datname.nspname.relname
List pgsql-hackers
I understand Tom's position to be that the behavior should be changed back,
since it was 1) unintentional; and 2) breaks legitimate use (when the datname
matches current_database).

I think there's an easy answer here that would satisfy everyone; two patches:
0001 to fix the unintentional behavior change;
0002 to reject garbage input: anything with more than 3 dot-separated
     components, or with 3 components where the first doesn't match
     current_database.

0001 would be backpatched to v14.

If it turns out there's no consensus on 0002, or if it were really hard for
some reason, or (more likely) nobody went to the bother to implement it this
year, then that's okay.

I would prefer if it errored if the datname didn't match the current database.
After all, it would've helped me to avoid making a confusing problem report.

-- 
Justin



pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: pg14 psql broke \d datname.nspname.relname
Next
From: Andres Freund
Date:
Subject: Re: [RFC] building postgres with meson