Re: pg14 psql broke \d datname.nspname.relname

Поиск
Список
Период
Сортировка
От Justin Pryzby
Тема Re: pg14 psql broke \d datname.nspname.relname
Дата
Msg-id 20211012165745.GM27491@telsasoft.com
обсуждение исходный текст
Ответ на Re: pg14 psql broke \d datname.nspname.relname  (Stephen Frost <sfrost@snowman.net>)
Ответы Re: pg14 psql broke \d datname.nspname.relname  (Robert Haas <robertmhaas@gmail.com>)
Re: pg14 psql broke \d datname.nspname.relname  (Robert Haas <robertmhaas@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Vik Fearing
Дата:
Сообщение: Re: pg14 psql broke \d datname.nspname.relname
Следующее
От: Andres Freund
Дата:
Сообщение: Re: [RFC] building postgres with meson