| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg14 psql broke \d datname.nspname.relname |
| Date: | 2021-10-12 16:57:45 |
| Message-ID: | 20211012165745.GM27491@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-10-12 16:59:26 | Re: [RFC] building postgres with meson |
| Previous Message | Vik Fearing | 2021-10-12 16:52:30 | Re: pg14 psql broke \d datname.nspname.relname |