pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: sachinkonde3@gmail.com
Subject: BUG #18789: logical replication slots are deleted after failovers
Date: Wed, 29 Jan 2025 12:24:34 +0000
Message-ID: <18789-0355be214b97e924@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      18789
Logged by:          Sachin Konde-Deshmukh
Email address:      sachinkonde3@gmail.com
PostgreSQL version: 17.2
Operating system:   Oracle Linux 8.9
Description:        

We are using 2 node PostgreSQL 17 HA setup using Patroni 4.0.4.
When I do failover 2nd or third time or more than once, it fails to transfer
or move logical replication slot to new Primary.
postgres=# select slot_name,slot_type, failover,
synced,confirmed_flush_lsn,active from pg_replication_slots;
     slot_name      | slot_type | failover | synced | confirmed_flush_lsn |
active
--------------------+-----------+----------+--------+---------------------+--------
psoel89pgcluster01 | physical  | f        | f      |                     |
t
mysub              | logical   | t        | t      | 0/4000AB8           |
t
(2 rows)
After First Failover -->
postgres=# select slot_name,slot_type, failover,
synced,confirmed_flush_lsn,active from pg_replication_slots;
     slot_name      | slot_type | failover | synced | confirmed_flush_lsn |
active
--------------------+-----------+----------+--------+---------------------+--------
psoel89pgcluster02 | physical  | f        | f      |                     |
t
mysub              | logical   | f        | f      | 0/50001E0           |
t
(2 rows)
After 2nd Failover -->
select slot_name,slot_type, failover, synced,confirmed_flush_lsn,active from
pg_replication_slots;
     slot_name      | slot_type | failover | synced | confirmed_flush_lsn |
active
--------------------+-----------+----------+--------+---------------------+--------
psoel89pgcluster01 | physical  | f        | f      |                     |
t
mysub              | logical   | f        | f      | 0/60002B0           |
t
After 3rd failover -->
postgres=# select slot_name,slot_type, failover,
synced,confirmed_flush_lsn,active from pg_replication_slots;
     slot_name      | slot_type | failover | synced | confirmed_flush_lsn |
active
--------------------+-----------+----------+--------+---------------------+--------
psoel89pgcluster02 | physical  | f        | f      |                     |
t
(1 row)
has context menu


has context menu



view thread (6+ messages)  latest in thread

Message-ID: <18789-0355be214b97e924@postgresql.org>
Permalink:  ../18789-0355be214b97e924@postgresql.org/
Also on:    postgresql.org/message-id/18789-0355be214b97e924@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, sachinkonde3@gmail.com
  Subject: Re: BUG #18789: logical replication slots are deleted after failovers
  In-Reply-To: <18789-0355be214b97e924@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox