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

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: 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-04 08:37:59
Message-ID: CAA4eK1+pear1rPsaEABKYAoAaJg4jna7Em0O=1hZV4tskYT5+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 4, 2022 at 1:07 PM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
> By convention, the tab-complete logical replication subscription
> parameters are listed in the COMPLETE_WITH lists in alphabetical
> order, but when the "disable_on_error" parameter was added this was
> not done.
>

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?

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shiy.fnst@fujitsu.com 2022-07-04 08:41:17 RE: Handle infinite recursion in logical replication setup
Previous Message Kyotaro Horiguchi 2022-07-04 08:31:46 Re: pgsql: dshash: Add sequential scan support.