You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! In our environment we have master and standy databases, on master databases we have logical replication slots.
How to manage logical replication slots in repmgr ? I mean sync them with standby after switchover.
Unfortunally I didn't find any information about it in documentation.
The text was updated successfully, but these errors were encountered:
Suhogruz
changed the title
logical repolication slots
logical replication slots
Jan 1, 2025
I think you should have a look at pg_failover_slots. It's a Postgres extension which I believe is available for most supported versions of Postgres (13 and up). If you use Postgres 17, it's built in the core (already available).
Thanks for advice!
We are testing switchover between two PostgreSQL servers (master - slave), both have 17 version and repmgr installed.
repmgr does not want to set primary_conninfo (with the dbname parameter inside) when standby database are starting.
And it does this every time during switching - it re-writes primary_conninfo.
If set the required primary_conninfo manually (with dbname), then the logical slot present on the reserve and everything looks great. But after the repmgr switchovers it disappears.
So far we can't understand why this is happening.
Hi! In our environment we have master and standy databases, on master databases we have logical replication slots.
How to manage logical replication slots in repmgr ? I mean sync them with standby after switchover.
Unfortunally I didn't find any information about it in documentation.
The text was updated successfully, but these errors were encountered: