You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature Request]: Create Apache Beam PostgreSQL I/O Connector with streaming support #39959
Feature: Support a native PostgreSQL I/O with streaming support.
Expectation: Create a a dedicated, high-performance PostgreSQL connector with native PostgreSQL streaming and write sinks that works with databases that are either self-hosted or managed.
Requirements: Main functionality will be to deliver the initial snapshot and stream continuity. It should be able to support native PostgreSQL binary protocol and handle transactional and non-transactional logical messages. Ability to support two-phase commit transactions. It must be able to handle TOAST columns in Beam runner-managed state without issuing point queries to the live database. Handling DDL changes in logical replication is hard but should be able to handle DDL changes or have guardrails around it. Finally it needs to do it at scale even for write sink to PostgreSQL.
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
I’m interested in contributing to the PostgreSQL I/O connector initiative and would like to explore a well-defined area where I can make a meaningful contribution.
Given the scope of this feature, I believe it would be valuable to first investigate the existing PostgreSQL I/O implementations and identify opportunities to improve streaming support, transaction handling, or write-sink reliability.
I’d be happy to start with a focused investigation, document the relevant design considerations, and propose a concrete implementation plan before proceeding with any code changes.
Would there be a particular component or outstanding requirement where an initial contribution would be most useful?
Activity
jk-shah commentedon Sep 1, 2026
Planning to .take-issue to develop it myself using modern tools.
[Feature] Add native Go PostgreSQLIO write sink and deadlock compactor
alisha-1000 commentedon Oct 23, 2026
Hello,
I’m interested in contributing to the PostgreSQL I/O connector initiative and would like to explore a well-defined area where I can make a meaningful contribution.
Given the scope of this feature, I believe it would be valuable to first investigate the existing PostgreSQL I/O implementations and identify opportunities to improve streaming support, transaction handling, or write-sink reliability.
I’d be happy to start with a focused investigation, document the relevant design considerations, and propose a concrete implementation plan before proceeding with any code changes.
Would there be a particular component or outstanding requirement where an initial contribution would be most useful?