Re: New standby_slot_names GUC in PG 17
От | Masahiko Sawada |
---|---|
Тема | Re: New standby_slot_names GUC in PG 17 |
Дата | |
Msg-id | CAD21AoCiywCQp8GTJiO4XVGSrNy5bESouE5H+BXpX_fMNt+zrQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: New standby_slot_names GUC in PG 17 (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
RE: New standby_slot_names GUC in PG 17
|
Список | pgsql-hackers |
On Tue, Jun 25, 2024 at 5:32 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > 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. Agreed. So +1 for synchronized_stnadby_slots. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: