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.96) (envelope-from ) id 1w8aPo-000gEY-3C for pgsql-announce@arkaria.postgresql.org; Fri, 03 Apr 2026 09:02:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w8aPn-00AM5V-2M for pgsql-announce@arkaria.postgresql.org; Fri, 03 Apr 2026 09:02:08 +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.96) (envelope-from ) id 1w8aPm-00AM5E-1t for pgsql-announce@lists.postgresql.org; Fri, 03 Apr 2026 09:02:07 +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.98.2) (envelope-from ) id 1w8aPk-00000000KSa-2oVK for pgsql-announce@lists.postgresql.org; Fri, 03 Apr 2026 09:02:06 +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=ftHDvkSdFlo6PIeyF+Iby739Widy1G13HhjFm7FEFW4=; b=kDoAg1Mg01ciUVEW6uIBw/LoIB rbHXwnb/MYyzGyb+ZyMCxo02ScSU5dv4HHgpexDOIVdk9eYyScsxZtKGSkeo3rq28RJitmPNEJ/rs 85f+Nd2Vgrd9WUx36jGe/T1NUrJVvpMmSxC3xSfE/P4DDxpgS12rzbyzIzNfwhezboJoEygpxoApr e34JB1Rxf9Xkr51H2+k30mjhSVAkl3OW4bR06e3YNxGBqKAUZVXpnux/owXM/CvyT53gdAt6HQ61B 9stidHHt/IBkb+PuoNN/nPG6a1+d96/7MpcwELScQd8MUJGhsz9YM02WtLIRpjgaTD/CpATD+6glw VgSwF1vw==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w8aPk-000uv3-0Z for pgsql-announce@lists.postgresql.org; Fri, 03 Apr 2026 09:02:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w8aPi-00EgdF-0i for pgsql-announce@lists.postgresql.org; Fri, 03 Apr 2026 09:02:03 +0000 Content-Type: multipart/alternative; boundary="===============3687403933687079780==" MIME-Version: 1.0 Subject: PostgreSQL CDC, Evolved: Read-Only Mode, IAM Auth & Partition Support Now in Estuary To: PostgreSQL Announce From: Estuary via PostgreSQL Announce Reply-To: sourabh@estuary.dev Date: Fri, 03 Apr 2026 09:01:14 +0000 Message-ID: <177520687482.3221092.17630158063825856170@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: proprietary X-pglister-tagsig: 62b5a87a187c6f254300b2dbebe945b553271a83427c7f62b7be6d3e1ccba7bf List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============3687403933687079780== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Estuary has released significant updates to its PostgreSQL connectors, expa= nding support for production-grade change data capture (CDC) use cases. ## What's New ### Read-Only Capture Estuary now supports CDC in read-only mode without needing to write to a wa= termarks table. Read-only captures should include a table with frequent upd= ates or a "heartbeat" table to ensure WAL retention doesn't grow continuous= ly. Read-only mode also allows capturing from a PostgreSQL standby replica, let= ting teams offload replication impact from the primary database entirely. C= apturing from read-only standbys requires: - PostgreSQL 16 or later - Logical decoding enabled - `hot_standby_feedback =3D on` to retain catalog metadata ### IAM Authentication Both PostgreSQL source and destination connectors now support IAM authentic= ation, enabling role-based access for teams running PostgreSQL on AWS, GCP,= or Azure. This removes the need to manage static database credentials in p= ipeline configurations. ### Partitioned Table Support A new advanced setting called **"Capture Partitioned Tables as Partitions"*= * allows each partition of a partitioned PostgreSQL table to be captured as= an individual stream, giving teams fine-grained control over how partition= ed data flows through their pipelines. ## Documentation & Resources For full setup instructions including WAL configuration, replication slot m= anagement, and platform-specific guides for Amazon RDS, Aurora, Google Clou= d SQL, and Azure Database for PostgreSQL: - [PostgreSQL Source Connector Documentation](https://docs.estuary.dev/refe= rence/Connectors/capture-connectors/PostgreSQL/) - [PostgreSQL Destination Connector Documentation](https://docs.estuary.dev= /reference/Connectors/materialization-connectors/PostgreSQL/) - [Get started free](https://dashboard.estuary.dev/register) | [Contact the= team](https://estuary.dev/contact-us/) --===============3687403933687079780== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PostgreSQL CDC, Evolved: Read-Only Mode, IAM Auth & Partitio= n Support Now in Estuary
 

PostgreSQL CDC, Evolved: Read-Only Mode, IAM Auth & Partition Sup= port Now in Estuary

Estuary has released significant updates to= its PostgreSQL connectors, expanding support for production-grade change d= ata capture (CDC) use cases.

What's New

Read-Only Capture

Estuary now supports CDC in read-only mode = without needing to write to a watermarks table. Read-only captures should i= nclude a table with frequent updates or a "heartbeat" table to ensure WAL r= etention doesn't grow continuously.

Read-only mode also allows capturing from a= PostgreSQL standby replica, letting teams offload replication impact from = the primary database entirely. Capturing from read-only standbys requires: - PostgreSQL 16 or later - Logical decoding enabled - hot_standby_feedback =3D on to retain catalog metadata

IAM Authentication

Both PostgreSQL source and destination conn= ectors now support IAM authentication, enabling role-based access for teams= running PostgreSQL on AWS, GCP, or Azure. This removes the need to manage = static database credentials in pipeline configurations.

Partitioned Table Support

A new advanced setting called "Capt= ure Partitioned Tables as Partitions" allows each partition of a p= artitioned PostgreSQL table to be captured as an individual stream, giving = teams fine-grained control over how partitioned data flows through their pi= pelines.

Documentation & Resources

For full setup instructions including WAL c= onfiguration, replication slot management, and platform-specific guides for= Amazon RDS, Aurora, Google Cloud SQL, and Azure Database for PostgreSQL:

This email was sent to you from Estuary. It was delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Estuary.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Proprietary. 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/.
 
--===============3687403933687079780==--