From: | Nisha Moond <nisha(dot)moond412(at)gmail(dot)com> |
---|---|
To: | Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com> |
Cc: | duffieldzane(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_copy_logical_replication_slot doesn't copy the failover property |
Date: | 2025-02-20 04:09:27 |
Message-ID: | CABdArM5EVkesP0ggypOOBG2Qu9udE_22VZD4tgAu0UqNnWdA2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Wed, Feb 19, 2025 at 12:40 PM Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com> wrote:
> Hi,
>
> The failover option is set to false by default while copying of the
> slots as it may cause some issue during slot synchronization as per
> discussion [1].
>
> I have created a patch to update the documentation for the same.
>
Thanks for the patch.
A couple of comments regarding the sentence:
+ not copied and set as <literal>false</literal> by default due to
+ potential issues with the slot synchronization.
1) / and set as/ and is set to
"set to" is more natural and clearer when assigning a specific value
compared to "set as."
2) "due to potential issues..." wording implies that it is addressing
existing issues. I feel it would be better to say:
"... <literal>false</literal> by default to avoid potential issues
with the slot synchronization."
--
Thanks,
Nisha
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2025-02-20 04:15:38 | Re: Streaming Replication vs Logical |
Previous Message | Amit Langote | 2025-02-19 07:26:33 | Re: Minor suggestions for docs regarding json_table |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2025-02-20 04:16:01 | Re: Commitfest app release on Feb 17 with many improvements |
Previous Message | Hayato Kuroda (Fujitsu) | 2025-02-20 04:08:05 | RE: Proposal: Filter irrelevant change before reassemble transactions during logical decoding |