public inbox for [email protected]
help / color / mirror / Atom feedset failover=true on existing logical replication slot PG18
4+ messages / 3 participants
[nested] [flat]
* set failover=true on existing logical replication slot PG18
@ 2026-06-19 15:24 Scot Kreienkamp <[email protected]>
2026-06-20 12:16 ` Re: set failover=true on existing logical replication slot PG18 Matthew Tice <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Scot Kreienkamp @ 2026-06-19 15:24 UTC (permalink / raw)
To: [email protected] <[email protected]>
Hello list,
I am trying to make use of the synchronized logical replication slots on PG18. I have all the requirements met, and if I create a logical replication slot manually with failover=true it is replicated to the second node. Unfortunately I have two connections that create their own logical replication slots with failover false. AWS DMS is one for example, but both have the same problem. Is there any way to change the failover parameter on an existing logical replication slot from false to true? Or set it so that all logical replications slots are synchronized so that they don't have to be individually created or altered for replication=true? Or force them all to true? Any other ideas?
Thanks!
Scot Kreienkamp | Applications Infrastructure Architect | La-Z-Boy Corporate
(734) 384-6403 | 1-734-915-1444 | [email protected]
One La-Z-Boy Drive | Monroe, Michigan 48162 | la-z-boy.com<http://www.la-z-boy.com/;
facebook.com/lazboy<http://facebook.com/lazboy; | instagram.com/lazboy<https://instagram.com/lazboy; | youtube.com/lazboy<http://youtube.com/lazboy;
[cid:lazboy_2024_inc_navy_4a4d68ec-613a-4141-a2aa-d73a2ae749f6.png]
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
Attachments:
[image/png] lazboy_2024_inc_navy_4a4d68ec-613a-4141-a2aa-d73a2ae749f6.png (4.3K, ../../SJ0PR15MB5245B5DA980217228FD9B7AC9AE22@SJ0PR15MB5245.namprd15.prod.outlook.com/3-lazboy_2024_inc_navy_4a4d68ec-613a-4141-a2aa-d73a2ae749f6.png)
download | view image
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: set failover=true on existing logical replication slot PG18
2026-06-19 15:24 set failover=true on existing logical replication slot PG18 Scot Kreienkamp <[email protected]>
@ 2026-06-20 12:16 ` Matthew Tice <[email protected]>
2026-06-22 05:44 ` RE: set failover=true on existing logical replication slot PG18 Hayato Kuroda (Fujitsu) <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Matthew Tice @ 2026-06-20 12:16 UTC (permalink / raw)
To: ; +Cc: [email protected] <[email protected]>
> On Jun 19, 2026, at 9:24 AM, Scot Kreienkamp <[email protected]> wrote:
>
> Hello list,
>
> I am trying to make use of the synchronized logical replication slots on PG18. I have all the requirements met, and if I create a logical replication slot manually with failover=true it is replicated to the second node. Unfortunately I have two connections that create their own logical replication slots with failover false. AWS DMS is one for example, but both have the same problem. Is there any way to change the failover parameter on an existing logical replication slot from false to true? Or set it so that all logical replications slots are synchronized so that they don’t have to be individually created or altered for replication=true? Or force them all to true? Any other ideas?
>
> Thanks!
>
I had the same problem recently with our Confluent-generated replication slots. I didn’t think there was but I just found this in the docs:
ALTER_REPLICATION_SLOT slot_name ( option [, ...] )
Change the definition of a replication slot. See Section 26.2.6 for more about replication slots. This command is currently only supported for logical replication slots.
slot_name
The name of the slot to alter. Must be a valid replication slot name (see Section 26.2.6.1).
The following option is supported:
FAILOVER [ boolean ]
If true, the slot is enabled to be synced to the standbys so that logical replication can be resumed after failover.
https://www.postgresql.org/docs/17/protocol-replication.html
53.4. Streaming Replication Protocol
postgresql.org
Attachments:
[image/png] elephant.png (64.3K, ../../[email protected]/3-elephant.png)
download | view image
^ permalink raw reply [nested|flat] 4+ messages in thread
* RE: set failover=true on existing logical replication slot PG18
2026-06-19 15:24 set failover=true on existing logical replication slot PG18 Scot Kreienkamp <[email protected]>
2026-06-20 12:16 ` Re: set failover=true on existing logical replication slot PG18 Matthew Tice <[email protected]>
@ 2026-06-22 05:44 ` Hayato Kuroda (Fujitsu) <[email protected]>
2026-06-22 13:42 ` RE: set failover=true on existing logical replication slot PG18 Scot Kreienkamp <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Hayato Kuroda (Fujitsu) @ 2026-06-22 05:44 UTC (permalink / raw)
To: 'Matthew Tice' <[email protected]>; +Cc: [email protected] <[email protected]>
Dear Matthew, Scot,
There are no ways to control default value of failover. Regarding the way for
changing the value, yes, ALTER_REPLICATION_SLOT replication command is an only
way to do that. Note that it's acceptable only when the backend is in the
replication mode - normal backend cannot understand them.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
^ permalink raw reply [nested|flat] 4+ messages in thread
* RE: set failover=true on existing logical replication slot PG18
2026-06-19 15:24 set failover=true on existing logical replication slot PG18 Scot Kreienkamp <[email protected]>
2026-06-20 12:16 ` Re: set failover=true on existing logical replication slot PG18 Matthew Tice <[email protected]>
2026-06-22 05:44 ` RE: set failover=true on existing logical replication slot PG18 Hayato Kuroda (Fujitsu) <[email protected]>
@ 2026-06-22 13:42 ` Scot Kreienkamp <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: Scot Kreienkamp @ 2026-06-22 13:42 UTC (permalink / raw)
To: Hayato Kuroda (Fujitsu) <[email protected]>; 'Matthew Tice' <[email protected]>; +Cc: [email protected] <[email protected]>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text -->
<style>.EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; }</style></head>
<body>
<font size="2"><div class="PlainText">"normal backend cannot understand them."<br>
<br>
Thank you Hayato, that's what I was missing. I got it working now.<br>
<br>
<p style="FONT-SIZE: 10pt; FONT-FAMILY: ARIAL"><span style="FONT-FAMILY: Calibri"><font face="HelveticaNeueLT Std"><span style="FONT-FAMILY: Calibri"><strong><br></strong></span></font></span></p><p style="FONT-SIZE: 10pt; FONT-FAMILY: ARIAL"><span style="FONT-FAMILY: Calibri"><font face="HelveticaNeueLT Std"><span style="FONT-FAMILY: Calibri"><strong>Scot Kreienkamp | Applications Infrastructure Architect | La-Z-Boy Corporate</strong></span><br style="FONT-SIZE: 9pt"><span style="FONT-SIZE: 9pt"><span style="FONT-FAMILY: Calibri">One La-Z-Boy Drive | Monroe, Michigan 48162</span>
| </span></font></span><span style="font-family: Calibri, sans-serif; font-size: 12px;"> (734) 384-6403 | 1-734-915-1444 | [email protected]</span><span style="FONT-FAMILY: Calibri"><font face="HelveticaNeueLT Std"><br></font></span></p>
<p style="FONT-SIZE: 10pt; FONT-FAMILY: ARIAL"><font face="Arial"><span style="FONT-FAMILY: HelveticaNeueLT Std"><span style="FONT-SIZE: 9pt"><span style="FONT-FAMILY: Wingdings"><span style="FONT-FAMILY: HelveticaNeueLT Std"></span></span></span></span></font> </p>
<br>
-----Original Message-----<br>
From: Hayato Kuroda (Fujitsu) <[email protected]> <br>
Sent: Monday, June 22, 2026 1:44 AM<br>
To: 'Matthew Tice' <[email protected]><br>
Cc: [email protected]<br>
Subject: RE: set failover=true on existing logical replication slot PG18<br>
<br>
Dear Matthew, Scot,<br>
<br>
There are no ways to control default value of failover. Regarding the way for<br>
changing the value, yes, ALTER_REPLICATION_SLOT replication command is an only<br>
way to do that. Note that it's acceptable only when the backend is in the<br>
replication mode - normal backend cannot understand them.<br>
<br>
Best regards,<br>
Hayato Kuroda<br>
FUJITSU LIMITED<br>
<br>
</div></font>
<P style="FONT-SIZE: 10pt; FONT-FAMILY: ARIAL">This message is intended only for
the individual or entity to which it is addressed. It may contain privileged,
confidential information which is exempt from disclosure under applicable laws.
If you are not the intended recipient, you are strictly prohibited from
disseminating or distributing this information (other than to the intended
recipient) or copying this information. If you have received this communication
in error, please notify us immediately by e-mail or by telephone at the above
number. Thank you. </P></body>
</html>
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2026-06-22 13:42 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-06-19 15:24 set failover=true on existing logical replication slot PG18 Scot Kreienkamp <[email protected]>
2026-06-20 12:16 ` Matthew Tice <[email protected]>
2026-06-22 05:44 ` Hayato Kuroda (Fujitsu) <[email protected]>
2026-06-22 13:42 ` Scot Kreienkamp <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox