From: | EDB via PostgreSQL Announce <announce-noreply(at)postgresql(dot)org> |
---|---|
To: | PostgreSQL Announce <pgsql-announce(at)lists(dot)postgresql(dot)org> |
Subject: | PG Failover Slots 1.1.0 Released |
Date: | 2024-08-28 06:37:51 |
Message-ID: | 172482707182.862888.2408495183659917565@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce |
### PG Failover Slots 1.1.0 Released
[EDB](https://www.enterprisedb.com) is pleased to announce the release of PG Failover Slots (pg_failover_slots) 1.1.0. This release includes support for the upcoming PostgreSQL 17, bug fixes, and additional configuration options. You can find PG Failover Slots on [GitHub](https://github.com/EnterpriseDB/pg_failover_slots), where you will also find the latest [Release notes](https://github.com/EnterpriseDB/pg_failover_slots/releases). PG Failover Slots is open-source software under the [PostgreSQL license](https://github.com/EnterpriseDB/pg_failover_slots?tab=License-1-ov-file#readme).
Designed for users with logical replication publications on Postgres databases that are part of a streaming replication architecture, PG Failover Slots avoids the need for logical replication subscribers to reseed their logical replication tables when the logical replication publisher is part of a physical streaming replication architecture, and a new standby gets promoted to primary.
Since the replication slot used by logical replication is only maintained on the primary node, downstream subscribers will not receive any new changes from the newly promoted primary until the slot is created. Picking up logical replication changes from the newly promoted standby is unsafe because the information that includes which data a subscriber has confirmed receiving and which log data still needs to be retained for the subscriber will have been lost, resulting in an unknown gap in data.
PG Failover Slots makes logical replication slots usable across a physical failover via the following features:
* Copies any missing replication slots from the primary to the standby
* Removes any slots from the standby that aren't found on the primary
* Periodically synchronizes the position of slots on the standby based on the primary
* Ensures that selected standbys receive data before any of the logical slot walsenders can send data to consumers
From | Date | Subject | |
---|---|---|---|
Next Message | fish's dotNET via PostgreSQL Announce | 2024-08-28 16:05:59 | Database .NET v36 released |
Previous Message | JDBC Project via PostgreSQL Announce | 2024-08-23 13:32:24 | PostgreSQL JDBC 42.7.4 Released |