Re: New standby_slot_names GUC in PG 17 - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: New standby_slot_names GUC in PG 17
Date
Msg-id CAA4eK1L+HKPswyYyFgf77nRwXxmhY1ifnHEbzv0TP3AXBczpWw@mail.gmail.com
Whole thread Raw
In response to Re: New standby_slot_names GUC in PG 17  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: New standby_slot_names GUC in PG 17
Re: New standby_slot_names GUC in PG 17
List pgsql-hackers
On Tue, Jun 25, 2024 at 12:30 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> On Tue, Jun 25, 2024 at 1:54 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
>
> > So, my
> > preference is in order as follows: synchronized_standby_slots,
> > wait_for_standby_slots, logical_replication_wait_slots,
> > logical_replication_synchronous_slots, and
> > logical_replication_synchronous_standby_slots.
>
> I also prefer synchronized_standby_slots.
>
> From a different angle just for discussion, is it worth considering
> the term 'failover' since the purpose of this feature is to ensure a
> standby to be ready for failover in terms of logical replication? For
> example, failover_standby_slot_names?
>

I feel synchronized better indicates the purpose because we ensure
such slots are synchronized before we process changes for logical
failover slots. We already have a 'failover' option for logical slots
which could make things confusing if we add 'failover' where physical
slots need to be specified.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Track the amount of time waiting due to cost_delay
Next
From: jian he
Date:
Subject: add a new explain option including_query for include query string inside the json plan output