Re: pg_copy_logical_replication_slot doesn't copy the failover property
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>
Cc: Shlok Kyal <shlok.kyal.oss@gmail.com>,
Masahiko Sawada <sawada.mshk@gmail.com>, Nisha Moond <nisha.moond412@gmail.com>, "duffieldzane@gmail.com" <duffieldzane@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-02-25T05:31:56Z
Lists: pgsql-hackers, pgsql-docs
On Mon, Feb 24, 2025 at 4:29 PM Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com> wrote: > > Here is the new V3 patch set which updated the comments to make the > issue clearer. > I pushed your first patch after minor modifications. > After thinking more on the two_phase option, I didn't find an issue that prevent > us from copying its option value. > Please see the comments atop ReplicationSlotCreate() and study the commit 19890a064ebf53dedcefed0d8339ed3d449b06e6 to understand the reasons as to why we initially enabled only at create time. It is possible that the risk mentioned in the commit doesn't hold true for copy_slot functionality but can you please analyze the same and let us know your thoughts on the same? > So, it’s more intuitive to me to just > copy its value instead of adding doc for it. The 0002 includes the same and I will > keep testing to ensure there are no other issues missed. > It is better to start a separate thread to discuss copying two_phase property. Even, if it ends with just some comments and doc change, it deserves an independent discussion. -- With Regards, Amit Kapila.
Commits
-
Doc: Fix pg_copy_logical_replication_slot description.
- 5b8f2ccc0a93 18.0 landed
- 7c906c5b46f8 17.5 landed
-
Add option to enable two_phase commits via pg_create_logical_replication_slot.
- 19890a064ebf 14.0 cited