apache/seatunnel

[Feature][connector-file] Add PostgreSQL COPY Command Support to JDBC Source for Enhanced Data Extraction Performance

Open

#10406 opened on Jan 28, 2026

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Java (6,897 stars) (1,432 forks)batch import
help wanted

Description

Search before asking

  • I had searched in the feature and found no similar feature requirement.

Description

The current JDBC Source connector cannot use PostgreSQL's native COPY command for data extraction, forcing users to rely on slower standard SELECT queries when reading large datasets. This results in unnecessarily long extraction times and inefficient resource usage during data synchronization from PostgreSQL.

Usage Scenario

Enable high-speed data extraction from PostgreSQL databases in SeaTunnel ETL/ELT jobs.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Tech stack
javapostgresqlsql
Domain
databasebackendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Java knowledgePostgreSQL COPY command understandingSeaTunnel connector architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine the existing JDBC Source connector implementation in the seatunnel connectors flink/jdbc module to understand the current query execution flow. Study PostgreSQL COPY command syntax and compare with standard SELECT. Review any available PostgreSQL dialect files in the connector. No maintainer comments or linked PRs exist, so the research is independent.