Re: Re-order "disable_on_error" in tab-complete COMPLETE_WITH

Поиск
Список
Период
Сортировка
От Peter Smith
Тема Re: Re-order "disable_on_error" in tab-complete COMPLETE_WITH
Дата
Msg-id CAHut+Ptbcgp05xR=aOjac9AUN3FSo2_BnkHAnJqWdMVrE0640A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Re-order "disable_on_error" in tab-complete COMPLETE_WITH  ("Euler Taveira" <euler@eulerto.com>)
Ответы Re: Re-order "disable_on_error" in tab-complete COMPLETE_WITH  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
On Mon, Jul 4, 2022 at 10:29 PM Euler Taveira <euler@eulerto.com> wrote:
>
> On Mon, Jul 4, 2022, at 5:37 AM, Amit Kapila wrote:
>
> Yeah, it seems we have overlooked this point. I think we can do this
> just for HEAD but as the feature is introduced in PG-15 so there is no
> harm in pushing it to PG-15 as well especially because it is a
> straightforward change. What do you or others think?
>
> No objection. It is a good thing for future backpatches.
>

Since there is no function change or bugfix here I thought it was only
applicable for HEAD. This change is almost in the same category as a
code comment typo patch - do those normally get backpatched? - maybe
follow the same convention here. OTOH, if you think it may be helpful
for future backpatches then I am also fine if you wanted to push it to
PG15.

------
Kind Regards,
Peter Smith.
Fujitsu Australia



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Daniel Gustafsson
Дата:
Сообщение: Re: TAP output format in pg_regress
Следующее
От: Andres Freund
Дата:
Сообщение: Re: TAP output format in pg_regress