pg_failover_slots
pg_failover_slots copied to clipboard
PG Failover Slots extension
Hello, I'm trying to use this extension with CNPG and i have no problem with basic configuration, however, i have a few questions. This is my context and configuration: *...
Currently failover slots are only synchronised from the primary to the standby(s), not the other way around. Postgres 16 has added support for cascading replication, where the active slot is...
Situation: a PostgreSQL 13 master/standby setup on-premises using repmgr. We recently added a logical standby, by the use of AWS Data Migration Server (DMS) to replicate to a cloud instance....
Greetings, Is it possible to provide a semi-universal example of the pg-failover-slots configuration. I try to do configuration according to existing documentation - replication slot(s) do not appear on the...
I kill the master node and the slave node took over the master node, but the original master node had the following error:  The replication slot is still available...
Instead of blocking indefinitely for a replication slot to be syncable, introduce a new GUC pg_failover_slots.sync_timeout after which we will move to the next one. To avoid waiting from scratch,...
We never know how long it will take for an inactive replication slot to advance. Hence, it doesn't make sense to wait for such slot as it will *not* allow...
This PR replaces the hardcoded WORKER_NAP_TIME by a GUC, and the hardcoded default database name "postgres" to another GUC.
Why is it necessary to configure primary_slot and how to ensure that synchronous data is not lost during node switching?
Currently we need the pg_config binary to build the pg_failover_slots extension/module. This PR makes changes to the Makefile so that it can be built from within the contrib folder without...