Make database connection pool size configurable #2

New Issue

2026-06-02T04:26:42Z

logaritmisk commented

2026-06-02 04:26:42 +00:00

Db::connect hardcodes PgPoolOptions::new().max_connections(5) (crates/db/src/lib.rs).

Pool sizing is operationally significant for the per-org-deployment model (total connections = sum of all org pools against the shared Postgres; see docs/specs/2026-06-02-mvp-architecture.md §3/§4). Promote it to configuration so it can be tuned per environment without an API change.

Accept pool size via config (e.g. a DbConfig { url, max_connections } or a Config field with a sensible default).
Thread it through server::run → Db::connect.

Source: Foundation (Plan 0) reviews — deferred, non-blocking.

`Db::connect` hardcodes `PgPoolOptions::new().max_connections(5)` (`crates/db/src/lib.rs`). Pool sizing is operationally significant for the per-org-deployment model (total connections = sum of all org pools against the shared Postgres; see `docs/specs/2026-06-02-mvp-architecture.md` §3/§4). Promote it to configuration so it can be tuned per environment without an API change. - [ ] Accept pool size via config (e.g. a `DbConfig { url, max_connections }` or a `Config` field with a sensible default). - [ ] Thread it through `server::run` → `Db::connect`. _Source: Foundation (Plan 0) reviews — deferred, non-blocking._

logaritmisk closed this issue

2026-06-04 20:10:20 +00:00

logaritmisk referenced this issue from a commit

2026-06-05 13:21:46 +00:00

docs(plans): tier 4 hardening batch 1 (#1 #2 #21)

logaritmisk referenced this issue from a commit

2026-06-05 13:21:46 +00:00

feat(server): configurable DB pool size via --db-max-connections/DB_MAX_CONNECTIONS (#2)

logaritmisk referenced this issue from a commit

2026-06-05 13:21:46 +00:00

merge: tier 4 hardening batch 1 (#1 #2 #21)

Sign in to join this conversation.