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 1wgPce-006Ai2-1c for pgsql-announce@arkaria.postgresql.org; Sun, 05 Jul 2026 16:23:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wgPcc-00CTnA-03 for pgsql-announce@arkaria.postgresql.org; Sun, 05 Jul 2026 16:23:10 +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 1wgPcb-00CTlO-0S for pgsql-announce@lists.postgresql.org; Sun, 05 Jul 2026 16:23:09 +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 1wgPcY-00000001euH-2Mnb for pgsql-announce@lists.postgresql.org; Sun, 05 Jul 2026 16:23:08 +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=LcJW7XGOLjwzz5JkIQvdsjUFaRXpaBkn+D7r/eVKvmM=; b=kVwqzN1qNqOG31syoWCjjWlg7X B3nIG7KcgYlNmzk2i4elil4csDjCz638/DqghLYmB4hJhlaLQ6jV+j1Vf+wU4f0uXyPiQS8FhwgKr IwgBGineFVNASg5Qgmw6DF5iJs1kgcGatYe+lFRlbWq7zcvf4qE56FO5PeeBg1HJGBPUaJ96SKAJi wDsiJS+VtotJUnk77uOBb+1CRfSKvhpbD+NZ8ScO3K+eMlCK3gRJp7XK0WW8fL9dKykRrmFjoeYSE Z5J7/zma3yRCVX7X8rVOGjuPuV8xSc4p33wWQAizRVQokENaTt7trgrMCcEE0Vb6U0ztHOoNiC7e1 454dJT9Q==; 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 1wgPcW-00B91C-2e for pgsql-announce@lists.postgresql.org; Sun, 05 Jul 2026 16:23:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wgPcV-00DK4G-28 for pgsql-announce@lists.postgresql.org; Sun, 05 Jul 2026 16:23:03 +0000 Content-Type: multipart/alternative; boundary="===============6171475211267629131==" MIME-Version: 1.0 Subject: pg-cdc Frustratingly simple Postgres change data capture to AWS S3 To: PostgreSQL Announce From: burnside project via PostgreSQL Announce Reply-To: hello@burnsideproject.ai Date: Sun, 05 Jul 2026 16:22:12 +0000 Message-ID: <178326853237.108999.11396238148836816033@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 8ae90230d3ef0dcbfce27f780432ddd5c55f6cefab34d345ecbd9ae4deb4bf86 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============6171475211267629131== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Core Features git Repo: [https://github.com/burnside-project/pg-cdc](https://github.com/b= urnside-project/pg-cdc)=20 pg-cdc is not just replication. pg-cdc streams Postgres Write Ahead Logs(WA= L) out of production Postgres into typed, immutable, time-travelable Iceber= g tables on S3 Registers each entities in the AWS Glue Catalog Gates every read with AWS Lake Formation tags =E2=80=94 so AI agents, analy= sts, and query engines consume governed data without ever touching the sour= ce database, and without database credentials. No JVM. One binary. No return path =E2=80=94 the WAL is one-way; Parquet is immutable. Agents p= hysically cannot write to production. No database credentials =E2=80=94 consumers authenticate via AWS IAM + Lake= Formation, never a connection string. Governed by default =E2=80=94 untagged data is invisible; Lake Formation ta= gs gate every read, down to the column. Time travel built in =E2=80=94 every flush is an Iceberg snapshot; CDC epoc= hs + immutable raw@ tags give historical queries with no database branc= hing. --===============6171475211267629131== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg-cdc Frustratingly simple Postgres change data capture to AWS = S3
 

pg-cdc Frustratingly simple Postgres change data capture to AWS S3

Core Features

git Repo: = https://github.com/burnside-project/pg-cdc

pg-cdc is not just replication. pg-cdc stre= ams Postgres Write Ahead Logs(WAL) out of production Postgres into typed, i= mmutable, time-travelable Iceberg tables on S3 Registers each entities in the AWS Glue Catalog Gates every read with AWS Lake Formation tags =E2=80=94 so AI agents, analy= sts, and query engines consume governed data without ever touching the sour= ce database, and without database credentials. No JVM. One binary.

No return path =E2=80=94 the WAL is one-way= ; Parquet is immutable. Agents physically cannot write to production. No database credentials =E2=80=94 consumers authenticate via AWS IAM + Lake= Formation, never a connection string. Governed by default =E2=80=94 untagged data is invisible; Lake Formation ta= gs gate every read, down to the column. Time travel built in =E2=80=94 every flush is an Iceberg snapshot; CDC epoc= hs + immutable raw@<ts> tags give historical queries with no database= branching.
This email was sent to you from burnside project. It was delivered on their= behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to burnside project.

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/.
 
--===============6171475211267629131==--