PostgreSQL 19
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by locating the cargo-pgrx configuration and build entry point used for PostgreSQL version support, then reproduce the Nix build described in the issue. Done means VectorChord can build against PostgreSQL 19 without the unexpected '--pg19' error; verify the result with the relevant build or integration checks.
Written by the indexing model from the issue text.
Description
Creating this issue to track support for PostgreSQL 19. No rush since it is still in beta, just wanted to have something to link back to.
cargo-pgrx needs to be updated to 0.19.0+: https://github.com/NixOS/nixpkgs/pull/531301
vectorchord> building '/nix/store/yzhgld57xz1a0b166dvjg3p0j9si964a-vectorchord-1.1.1.drv'
vectorchord> Running phase: unpackPhase
vectorchord> unpacking source archive /nix/store/kasc9fxiz9sirz91qy4cw9bi3p3ncsiw-source
vectorchord> source root is source
vectorchord> Executing cargoSetupPostUnpackHook
vectorchord> Finished cargoSetupPostUnpackHook
vectorchord> Running phase: patchPhase
vectorchord> Executing cargoSetupPostPatchHook
vectorchord> Validating consistency between /build/source/Cargo.lock and /build/vectorchord-1.1.1-vendor/Cargo.lock
vectorchord> Finished cargoSetupPostPatchHook
vectorchord> Running phase: updateAutotoolsGnuConfigScriptsPhase
vectorchord> Running phase: configurePhase
vectorchord> Running phase: buildPhase
vectorchord> Executing cargo-pgrx buildPhase
vectorchord> error: unexpected argument '--pg19' found
vectorchord>
vectorchord> tip: a similar argument exists: '--pg18'
vectorchord>
vectorchord> Usage: cargo pgrx init --pg18 <PG18>
vectorchord>
vectorchord> For more information, try '--help'.
- Dominant language
- Rust
- Stars
- 1.8k
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
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 supervc-stack/VectorChord
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
supervc-stack/VectorChord#470 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
supervc-stack/VectorChord#469 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
supervc-stack/VectorChord#463 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
supervc-stack/VectorChord#459 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
supervc-stack/VectorChord#458 ·
All issues in supervc-stack/VectorChord
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
ajeetraina/awesome-docker-sbx#220 ·
-
`helios / deploy`: switch zone wait in `deploy.sh` has almost no headroom over healthy startup timesOpenTest Flake
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
oxidecomputer/omicron#11453 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
[Feature] 设置里面的同步功能Openenhancement user-priority/P2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
agent:triaged bug bughunt pm:npm priority:p1
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
SocketDev/socket-patch#1127 · 1 comment ·
Maintainers usually reply within 1 day