Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjCJp-00GI5q-2Y for pgsql-announce@arkaria.postgresql.org; Wed, 28 Aug 2024 06:38:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sjCJn-000Y5g-78 for pgsql-announce@arkaria.postgresql.org; Wed, 28 Aug 2024 06:38:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjCJm-000Y4m-9I for pgsql-announce@lists.postgresql.org; Wed, 28 Aug 2024 06:38:10 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjCJi-001no6-Ln for pgsql-announce@lists.postgresql.org; Wed, 28 Aug 2024 06:38:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=i/frW+VkszwxUGwm8GzUaY97ThAbbPQGnNZ9+FA6TV4=; b=ng0HYGHjXtN2sLq19w1X7OlJLj krPhuLbzsa4Ia3Gk6lPx7aZIoS+0t2s0BP6iWoKGHEIdFUNiCbBBE5J8gOwFXIsmBupjGnY+0U2Ha x0MJer/7tu2HFoN0y/G7QbonJc9wZvNYYrbDvuo3M4pEUfqEfKTvCbOV17JA6GWAMFNc3XPxW60yE fn8MGt7Pz5Jl5n6BuzK0P9bYWrDCSkCKFp5SPlKGww+oEpGRk7QtFf/gQEjbs/QZrpOKdBzsplw+1 UuASylZd1Ue6kj56VKMJxqZ+CU3V+uaCYewvXwzWJUprwxT3Zac/py9g8oVPnSr3Sk4KnKV2x+OVz iZppoCxw==; Received: from wrigleys.postgresql.org ([217.196.149.60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjCJh-0062lp-LX for pgsql-announce@lists.postgresql.org; Wed, 28 Aug 2024 06:38:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sjCJf-007eUB-2T for pgsql-announce@lists.postgresql.org; Wed, 28 Aug 2024 06:38:03 +0000 Content-Type: multipart/mixed; boundary="===============8019132592928414443==" MIME-Version: 1.0 Subject: PG Failover Slots 1.1.0 Released To: PostgreSQL Announce From: EDB via PostgreSQL Announce Reply-To: adam.wright@enterprisedb.com Date: Wed, 28 Aug 2024 06:37:51 +0000 Message-ID: <172482707182.862888.2408495183659917565@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: da6376886fe1d61af8af2e385a8864a596a2414a2421c3eb09b317133c2817c1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============8019132592928414443== Content-Type: multipart/alternative; boundary="===============3103012665403332828==" MIME-Version: 1.0 --===============3103012665403332828== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ### PG Failover Slots 1.1.0 Released [EDB](https://www.enterprisedb.com) is pleased to announce the release of P= G Failover Slots (pg_failover_slots) 1.1.0. This release includes support f= or the upcoming PostgreSQL 17, bug fixes, and additional configuration opti= ons. You can find PG Failover Slots on [GitHub](https://github.com/Enterpr= iseDB/pg_failover_slots), where you will also find the latest [Release note= s](https://github.com/EnterpriseDB/pg_failover_slots/releases). PG Failover= Slots is open-source software under the [PostgreSQL license](https://githu= b.com/EnterpriseDB/pg_failover_slots?tab=3DLicense-1-ov-file#readme). Designed for users with logical replication publications on Postgres databa= ses that are part of a streaming replication architecture, PG Failover Slot= s avoids the need for logical replication subscribers to reseed their logic= al replication tables when the logical replication publisher is part of a p= hysical streaming replication architecture, and a new standby gets promoted= to primary. Since the replication slot used by logical replication is only maintained o= n the primary node, downstream subscribers will not receive any new changes= from the newly promoted primary until the slot is created. Picking up logi= cal replication changes from the newly promoted standby is unsafe because t= he information that includes which data a subscriber has confirmed receivin= g and which log data still needs to be retained for the subscriber will hav= e been lost, resulting in an unknown gap in data.=20 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 t= he primary * Ensures that selected standbys receive data before any of the logical slo= t walsenders can send data to consumers --===============3103012665403332828== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PG Failover Slots 1.1.0 Released
 

PG Failover Slots 1.1.0 Released

PG Failover Slots 1.1.0 Release= d

EDB is pleased to an= nounce the release of PG Failover Slots (pg_failover_slots) 1.1.0. This rel= ease includes support for the upcoming PostgreSQL 17, bug fixes, and additi= onal configuration options. You can find PG Failover Slots on GitHub, where you will also find the latest= Release notes. PG Fai= lover Slots is open-source software under the PostgreSQL license.

Designed for users with logical replication= publications on Postgres databases that are part of a streaming replicatio= n architecture, PG Failover Slots avoids the need for logical replication s= ubscribers to reseed their logical replication tables when the logical repl= ication 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 prom= oted standby is unsafe because the information that includes which data a s= ubscriber has confirmed receiving and which log data still needs to be reta= ined 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 miss= ing replication slots from the primary to the standby
  • Removes any slo= ts from the standby that aren't found on the primary
  • Periodically sy= nchronizes the position of slots on the standby based on the primary
  • Ensures that se= lected standbys receive data before any of the logical slot walsenders can = send data to consumers
This email was sent to you from EDB. It was delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to EDB.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============3103012665403332828==-- --===============8019132592928414443==--