COPY DATABASE fails on v1.0.0 and segfaults on v1.1.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, postgresql
- Domain
- databases
Research direction
No source files or tests are named. Start by reproducing the two COPY FROM DATABASE commands against PostgreSQL 12.19 on macOS, comparing v1.0.0's unsupported Index error with v1.1.0's segmentation fault. Done means the database copy completes without a crash or unsupported-index error and does not leave a stray .wal file.
Written by the indexing model from the issue text.
Description
What happens?
I can connect to and copy tables from a PostgreSQL (running in Docker on my laptop), but if I try to copy the database I get a segmentation fault on v1.1.0, leaving behind a .wal file.
On v1.0.0 I get Not implemented Error: Entry type Index not supported in PhysicalCopyDatabase.
I don't imagine the steps I've shown to reproduce it will be much help. Let me know what I can do to help you narrow it down.
To Reproduce
$ duckdb pg_local.duckdb
v1.1.0 fa5c2fe15f
Enter ".help" for usage hints.
D ATTACH 'postgresql://[email protected]:5435/tqc' AS tqc (TYPE POSTGRES);
D COPY FROM DATABASE tqc TO pg_local;
zsh: segmentation fault duckdb pg_local.duckdb
$ duckdb-1.0 pg_local.duckdb
v1.0.0 1f98600c2c
Enter ".help" for usage hints.
D ATTACH 'postgresql://[email protected]:5435/tqc' AS tqc (TYPE POSTGRES);
D COPY FROM DATABASE tqc TO pg_local;
Not implemented Error: Entry type Index not supported in PhysicalCopyDatabase
OS:
MacOS
PostgreSQL Version:
12.19
DuckDB Version:
1.1.0
DuckDB Client:
duckdb
Full Name:
James Gilbert
Affiliation:
Wellcome Sanger Institute
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
- 372
- Forks
- 107
- Avg merge
- 13h 55m
- Merged PRs (30d)
- 13
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from duckdb/duckdb-postgres
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-postgres#575 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
duckdb/duckdb-postgres#564 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
duckdb/duckdb-postgres#491 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-postgres#487 · 1 comment ·
Maintainers usually reply within 1 day
-
After `COPY DATABASE FROM <pg>`, the types from pg are improperly formatted in `EXPORT` commandsOpen
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-postgres#429 ·
Maintainers usually reply within 1 day
All issues in duckdb/duckdb-postgres
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
hipRTC lit tests compile against /opt/rocm's LLVM instead of the ROCm under test (ci/ hardcodes LLVM_PATH)Possibly taken @bernardogv claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
brndnmtthws/conky#2486 ·
Maintainers usually reply within 1 day
-
請增加教學：數字後的句號Open
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100