Re: pg14 psql broke \d datname.nspname.relname
От | Robert Haas |
---|---|
Тема | Re: pg14 psql broke \d datname.nspname.relname |
Дата | |
Msg-id | CA+TgmoZWGneZAM+-L1zHvEOOb_4HS7WxhPmAOkjFQ-onG-_ySA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg14 psql broke \d datname.nspname.relname (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: pg14 psql broke \d datname.nspname.relname
|
Список | pgsql-hackers |
On Tue, Oct 12, 2021 at 12:57 PM Justin Pryzby <pryzby@telsasoft.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
В списке pgsql-hackers по дате отправления: