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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com>
Cc: 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Re-order "disable_on_error" in tab-complete COMPLETE_WITH
Date: 2022-07-06 03:42:29
Message-ID: YsUEpesLQJ+RfNOE@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 06, 2022 at 02:48:07AM +0000, osumi(dot)takamichi(at)fujitsu(dot)com wrote:
> On Tuesday, July 5, 2022 1:05 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> It can help if there is any bug-fix in the same code path or if some other code
>> adjustment in the same area is required in the back branch.
>> I feel the chances of both are less but I just wanted to keep the code consistent
>> for such a possibility. Anyway, I'll wait for a day or so and see if anyone has
>> objections to it.
>
> I also agree with pushing it to PG-15 for comfortability of future backpatches.

Yeah, backpatching that is just but fine.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-07-06 03:47:10 Re: AIX support - alignment issues
Previous Message Amit Kapila 2022-07-06 03:36:13 Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication