feat(cmd/duckgres-worker): add a worker-only entry point that ships libduckdb#500
Merged
fuziontech merged 1 commit intomainfrom May 1, 2026
Merged
feat(cmd/duckgres-worker): add a worker-only entry point that ships libduckdb#500fuziontech merged 1 commit intomainfrom
fuziontech merged 1 commit intomainfrom
Conversation
…ibduckdb Counterpart to cmd/duckgres-controlplane (PR #498). This binary: - Links libduckdb (verified: go list -deps shows duckdb-go-bindings, duckdb-go/v2 in the import graph). - Imports duckdbservice but not controlplane — no PG wire surface, no config-store / k8s pool wiring. It's the runtime that the control plane spawns into worker pods over Unix sockets / TCP. - Is the target of the planned per-DuckDB-version matrix build in CI. A worker pod ships exactly one DuckDB version, pinned via go.mod + the Dockerfile DUCKDB_EXTENSION_VERSION build arg. Like cmd/duckgres-controlplane, this is a stub that errors out at runtime — duckgres' YAML / CLI / env config resolution still lives in the package main file at the repo root alongside the all-in-one binary. The follow-up PR lifts that into a shared package both new binaries can import. The point of this PR is locking in the binary's existence and the import-graph contract. Together with PR #498 (CP-only, no libduckdb) and PR #499 (CI guard), the binary split is now structurally complete: cmd/duckgres-controlplane no libduckdb (CP-only, all DuckDB versions run on remote workers) cmd/duckgres-worker links libduckdb (worker-only, pinned to one DuckDB version per build) duckgres all-in-one (links libduckdb, all modes) Verified: - go build ./cmd/duckgres-worker/... clean - go list -deps ./cmd/duckgres-worker | grep duckdb-go shows the expected DuckDB driver imports - go list -deps ./cmd/duckgres-controlplane | grep duckdb-go is still empty (the CP-only contract held) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Counterpart to
cmd/duckgres-controlplane(PR #498). This binary:go list -depsshows duckdb-go-bindings, duckdb-go/v2 in the import graph).duckdbservicebut notcontrolplane— no PG wire surface, no config-store / k8s pool wiring. It's the runtime that the control plane spawns into worker pods over Unix sockets / TCP.go.mod+ the DockerfileDUCKDB_EXTENSION_VERSIONbuild arg.Like
cmd/duckgres-controlplane, this is a stub that errors out at runtime — duckgres' YAML / CLI / env config resolution still lives in thepackage mainfile at the repo root alongside the all-in-one binary. The follow-up PR lifts that into a shared package both new binaries can import. The point of this PR is locking in the binary's existence and the import-graph contract.Where the binary split now stands
Together with PR #498 (CP-only, no libduckdb) and PR #499 (CI guard), the binary split is structurally complete:
cmd/duckgres-controlplanecmd/duckgres-workerduckgres(all-in-one)Test plan
go build ./cmd/duckgres-worker/...cleango list -deps ./cmd/duckgres-worker | grep duckdb-goshows the expected DuckDB driver importsgo list -deps ./cmd/duckgres-controlplane | grep duckdb-gois still empty (the CP-only contract held — also enforced by the CI guard from PR ci: guard cmd/duckgres-controlplane against duckdb-go regressions #499)🤖 Generated with Claude Code