Re: Disallow changing slot's failover option in transaction block
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: shveta malik <shveta.malik@gmail.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>
Date: 2024-04-18T23:34:49Z
Lists: pgsql-hackers
On Thu, Apr 18, 2024 at 11:22:24AM +0530, Amit Kapila wrote: > +1 for option 2 as it sounds logical to me and consistent with ALTER > SUBSCRIPTION. BTW, IIUC, you are referring to: "When altering the > slot_name, the failover and two_phase property values of the named > slot may differ from the counterpart failover and two_phase parameters > specified in the subscription. When creating the slot, ensure the slot > properties failover and two_phase match their counterpart parameters > of the subscription." in docs [1], right? FWIW, I'd also favor option 2, mostly on consistency ground as it would offer a better user-experience. On top of that, you're saying that may lead to some simplifications in the CREATE path. Without a patch, it's hard to tell, though. As far as I can see, this is not tracked as an open item and it should be. So I have added one. -- Michael
Commits
-
Fix the handling of the failover option in subscription commands.
- b29cbd3da4e3 17.0 landed