| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, 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 17:03:29 |
| Message-ID: | CA+TgmoZWGneZAM+-L1zHvEOOb_4HS7WxhPmAOkjFQ-onG-_ySA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 12, 2021 at 12:57 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> 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.
This might work, but I fear that 0001 would end up being substantially
more complicated than a combined patch that solves both problems
together.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-10-12 17:17:34 | Re: [RFC] building postgres with meson |
| Previous Message | Robert Haas | 2021-10-12 17:01:14 | Re: pg14 psql broke \d datname.nspname.relname |