Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Parallel COPY to Postgres ?

Open
#185 3 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
postgresql
Domain
databases

Research direction

Start by reproducing the ATTACH and COPY commands from the issue with PostgreSQL 16 and DuckDB v0.10.0, then inspect the postgres_scanner path handling COPY. Done means the documented multi-file import can use parallel PostgreSQL COPY processes, or the supported limitation is clearly established.

Written by the indexing model from the issue text.

Description

enhancement
What happens?

Hello,
I tried to do a parallel import in Postgres.
I wonder if postgres_scanner allows this ?

To Reproduce

I tried :

ATTACH 'user=postgres host=/var/run/postgresql port=5440' AS db (TYPE postgres);
COPY db.votes2 FROM 'data.zstd/*' (FORMAT parquet);

I tried to change file format (csv, parquet), compression, multiples files...
I also tried to first import in duckdb, then, copy to Postgres.
I only see one COPY process on Postgres.

OS:

Linux

PostgreSQL Version:

16

DuckDB Version:

v0.10.0 20b1486d11

DuckDB Client:

CLI

Full Name:

Adrien Nayrat

Affiliation:

Self Employed

Have you tried this on the latest main branch?
  • I agree
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
  • I agree
Dominant language
C++
Stars
375
Forks
113
Avg merge
5h 29m
Merged PRs (30d)
37

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from duckdb/duckdb-postgres

All issues in duckdb/duckdb-postgres

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.