LOAD duckpgq fails on DuckDB v1.5.1 with 'vector' exception

[vyasraos]

Description

LOAD duckpgq fails on DuckDB v1.5.1 (macOS arm64) with an initialization error.

Steps to Reproduce

INSTALL duckpgq FROM community;  -- succeeds
LOAD duckpgq;                    -- fails

Error

Invalid Input Error: Initialization function "duckpgq_duckdb_cpp_init" from file 
"/Users/<user>/.duckdb/extensions/v1.5.1/osx_arm64/duckpgq.duckdb_extension" 
threw an exception: "vector"

Environment

• DuckDB version: v1.5.1
• Platform: macOS arm64 (Darwin 24.6.0)
• Node API: @duckdb/node-api@1.5.1-r.1
• Also tested via: bun 1.3.0

Notes

• INSTALL succeeds and the extension appears in duckdb_extensions() as installed but not loaded
• Deleting the cached extension and reinstalling produces the same error
• The extension worked on earlier DuckDB versions (per community reports)

[vyasraos]

Update: Confirmed this is not Node.js-specific. Same error in the DuckDB CLI (v1.5.1, macOS arm64 via Homebrew):

$ duckdb --version
v1.5.1

$ duckdb -c "INSTALL duckpgq FROM community; LOAD duckpgq;"
Invalid Input Error: Initialization function "duckpgq_duckdb_cpp_init" from file 
"/Users/<user>/.duckdb/extensions/v1.5.1/osx_arm64/duckpgq.duckdb_extension" 
threw an exception: "vector"

Minimal reproduction:

brew install duckdb  # installs v1.5.1
rm -rf ~/.duckdb/extensions/*/osx_arm64/duckpgq*
duckdb -c "INSTALL duckpgq FROM community; LOAD duckpgq;"

[nicolas-geysse]

Confirming the same issue on linux_amd64 via @duckdb/node-api@1.5.1-r.1.

On Linux the behavior is a SIGSEGV (exit code 139) rather than the "vector" exception:

Step 5: Load duckpgq
[SIGSEGV - process killed]

• DuckDB version: v1.5.1
• Platform: linux_amd64 (WSL2, kernel 6.6.87.2)
• Node API: @duckdb/node-api@1.5.1-r.1
• Extension version: 78c7a6c (from community)

INSTALL duckpgq FROM community succeeds. LOAD duckpgq crashes immediately.

Works fine on DuckDB v1.5.0 with aec2e25.

[nicolas-geysse]

Still reproducing on linux_amd64 today (2026-06-17), DuckDB v1.5.1 (7dbb2e646f) via @duckdb/node-api@1.5.1-r.2 — INSTALL ok, LOAD SIGSEGVs (exit 139).

Worth flagging the wider state: DuckDB has since shipped 1.5.2, 1.5.3 and 1.5.4 (today), and none of them have a DuckPGQ binary at all (all 404 on the CDN). The only published binary is 1.5.1, which still crashes.

#307 has a root-cause fix (the EXTENSION_STATIC_BUILD ABI issue) that's marked mergeable but has sat unmerged for ~2 months — I bumped it there with a fresh minimal repro. Cross-linking here for the reporters following this issue.

[nicolas-geysse]

Resolved on DuckDB 1.5.4 ✅ — the community binary built on 2026-06-30 (f386a6cf) loads cleanly.

Verified on linux_amd64 via @duckdb/node-api@1.5.4-r.1 (2026-07-03):

INSTALL duckpgq FROM community;  -- ok
LOAD duckpgq;                    -- ok, no crash 🎉

CREATE PROPERTY GRAPH + GRAPH_TABLE queries all work; we've run a full 510-test suite against 1.5.4 with zero regressions. Note that 1.5.1–1.5.3 never got working binaries, so the practical fix is to move directly to DuckDB ≥ 1.5.4.

I've closed my related PR #307 as superseded. From our side this issue can be closed too. Big thanks to @Dtenwolde for the 1.5.2→1.5.4 build push! 🙏

[Dtenwolde]

You're welcome, glad to hear it's working!

[Dtenwolde]

I've asked the maintainers of the community extension build pipeline to also backfill DuckPGQ such that it can also be loaded through install duckpgq from community for v1.5.1, v1.5.2, and v1.5.3. But no news yet

[nicolas-geysse]

Thanks for the follow-up! No urgency on our side — we've already moved our production stack to 1.5.4 and everything works great. The backfills would mainly help users pinned to intermediate DuckDB versions (lockfiles, distro constraints). Happy to re-verify the backfilled binaries on linux_amd64 when they land — just ping this thread. Thanks again for the quick turnaround on 1.5.4!