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 1u9e2k-004OCa-CN for pgsql-announce@arkaria.postgresql.org; Tue, 29 Apr 2025 06:02:11 +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 1u9e2g-0058hV-Ur for pgsql-announce@arkaria.postgresql.org; Tue, 29 Apr 2025 06: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.94.2) (envelope-from ) id 1u9e2f-0058hE-Lc for pgsql-announce@lists.postgresql.org; Tue, 29 Apr 2025 06:02:06 +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.96) (envelope-from ) id 1u9e2e-0007vz-2T for pgsql-announce@lists.postgresql.org; Tue, 29 Apr 2025 06:02:05 +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=f/z8pNv95OsLB1qVeMFen4WX7yb3TszhI/yxxrr7dXE=; b=KQg05pHDN6J1G8R4N5oMJkWeHq QbmFpdgBT6BPWNJNR1rTGGKg+VOdaW1mjRGgu99C+g7ul4vrfN38ARoC50MjlBd4hU/UEoynMLiG0 C4HfZhnhli78hagch20XXmzruSVEsC6w1CgCsKK6w0xAYOOBGWG0QDyoildnbfU5fpGn6McKVwUCr +x2q/dAGsrspeJbi7sfd3l9V8QX+yCSkUVZcPr/W4T7xq7whr+ZBRyBDMdBRdumBOVmDBb4WkwwAJ bUgDdytdJ1icNFbVG8nNQfk1kYjjRYed1Qx9T89+tPK9upxUEugg8WdHSa3hiuOxGkKrL1PI7Bp0G DIXm7FEw==; 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.94.2) (envelope-from ) id 1u9e2d-007JmW-Hp for pgsql-announce@lists.postgresql.org; Tue, 29 Apr 2025 06:02:04 +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 1u9e2c-000sLS-Cx for pgsql-announce@lists.postgresql.org; Tue, 29 Apr 2025 06:02:03 +0000 Content-Type: multipart/mixed; boundary="===============8486796553128521572==" MIME-Version: 1.0 Subject: Streaming Data into Postgres with Estuary To: PostgreSQL Announce From: Estuary Flow via PostgreSQL Announce Reply-To: sourabh@estuary.dev Date: Tue, 29 Apr 2025 06:01:37 +0000 Message-ID: <174590649719.671.15681491565241312845@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: proprietary X-pglister-tagsig: cf3d837b32ff22377db4568585054af121bc648266af90d96a280c380a72d37a List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============8486796553128521572== Content-Type: multipart/alternative; boundary="===============3409482683807054740==" MIME-Version: 1.0 --===============3409482683807054740== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Estuary now provides native support for **real-time data streaming into Pos= tgreSQL** via its PostgreSQL materialization connector. With this, users ca= n configure Flow collections to automatically write into PostgreSQL tables = =E2=80=94 in seconds, at scale, and with exactly-once semantics. Whether you=E2=80=99re using a self-hosted Postgres instance or a managed d= atabase like **Amazon RDS**, **Google Cloud SQL**, or **Azure Database for = PostgreSQL**, Estuary ensures secure and reliable connectivity =E2=80=94 in= cluding support for **SSL** and **SSH tunneling**. ### Key Features: - Automatically creates target tables for each collection - Supports **standard and delta updates** - Handles schema evolution and reserved Postgres keywords - Preserves column capitalization and converts data types (e.g., `ipv4`, `m= acaddr`, `duration`) - Open-source compatible with Docker image: =20 `ghcr.io/estuary/materialize-postgres:dev` This connector is part of Estuary Flow =E2=80=94 a real-time data platform = that bridges Postgres with upstream systems like Kafka, MongoDB, APIs, and = more. =F0=9F=93=98 [Documentation: Streaming into PostgreSQL with Estuary](https:= //docs.estuary.dev/reference/Connectors/materialization-connectors/PostgreS= QL/) =20 =F0=9F=9A=80 [Get started with Estuary Flow](https://dashboard.estuary.dev)= =20 =F0=9F=94=A7 [Contact the team](https://estuary.dev/contact-us/) --===============3409482683807054740== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Streaming Data into Postgres with Estuary
 

Streaming Data into Postgres with Estuary

Estuary now provides native support for real-time data streaming into PostgreSQL via its PostgreSQL m= aterialization connector. With this, users can configure Flow collections t= o automatically write into PostgreSQL tables =E2=80=94 in seconds, at scale= , and with exactly-once semantics.

Whether you=E2=80=99re using a self-hosted = Postgres instance or a managed database like Amazon RDS, <= strong>Google Cloud SQL, or Azure Database for PostgreSQL<= /strong>, Estuary ensures secure and reliable connectivity =E2=80=94 includ= ing support for SSL and SSH tunneling.

Key Features:

  • Automatically c= reates target tables for each collection
  • Supports standard and delta updates
  • Handles schema = evolution and reserved Postgres keywords
  • Preserves colum= n capitalization and converts data types (e.g., ipv4, ma= caddr, duration)
  • Open-source com= patible with Docker image:
    ghcr.io/estuary/materialize-postgres:dev

This connector is part of Estuary Flow =E2= =80=94 a real-time data platform that bridges Postgres with upstream system= s like Kafka, MongoDB, APIs, and more.

=F0=9F=93=98 Documentation: Streaming into = PostgreSQL with Estuary
=F0=9F=9A=80 Get started with Estuary Flow
=F0=9F=94=A7 Contact the team
This email was sent to you from Estuary Flow. It was delivered on their beh= alf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Estuary Flow.

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/.
 
--===============3409482683807054740==-- --===============8486796553128521572==--