Re: Synchronizing slots from primary to standby
От | Amit Kapila |
---|---|
Тема | Re: Synchronizing slots from primary to standby |
Дата | |
Msg-id | CAA4eK1+X+sS2nnnkZ8oP=pfy+=ZxjD6umbRNAUQ4JWKh4fW0cQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Synchronizing slots from primary to standby (Peter Smith <smithpb2250@gmail.com>) |
Список | pgsql-hackers |
On Wed, Jan 31, 2024 at 10:40 AM Peter Smith <smithpb2250@gmail.com> wrote: > > On Wed, Jan 31, 2024 at 2:18 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > > > > > I think is correct to say all those *other* properties (create_slot, > > > enabled, copy_data) are forced to false because those otherwise have > > > default true values. > > > > > > > So, won't when connect=false, the user has to explicitly provide such > > values (create_slot, enabled, etc.) as false? If so, is using 'force' > > strictly correct? > > Perhaps the original docs text could be worded differently; I think > the word "force" here just meant setting connection=false > forces/causes/makes those other options behave "as if" they had been > set to false without the user explicitly doing anything to them. > Okay, I see your point. Let's remove the 'failover' from this part of the sentence. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: