[aesslinger]

Bumps version to 1.0.0-rc.12 in Cargo.toml, Cargo.lock, .tabularium, and CHANGELOG.md.

Included since rc.11

Fixed:

• rc.11 still hangs on direct (non-pooler) connections for tables with enum columns; 4 stuck workers then block ping/connect for every connection #166/fix: pre-resolve column types on direct connections to stop enum-table hang (#166) #168 — Direct-connection result-set queries on non-builtin column types (custom enum/composite/domain/range/extension types) no longer hang on large results. Pre-resolves column types via prepare on the shared cached client before the query_typed data fetch (the rc.11 fix only covered the transaction-pooler path).
• Batch/session path on a transaction pooler still deadlocks on non-builtin column types #169/fix: pre-resolve column types on batch/session pooler path (#169) #172 — Batch / interactive-transaction-session result-set queries on a transaction-mode pooler no longer deadlock on wide non-builtin-typed tables. run_batch_in_session now makes the same per-query routing decision as the single-query path (in_transaction pre-resolves on the shared client; no open transaction routes to the one-shot pinned path).
• Bare [SET/CREATE TEMP, SELECT] batch on a transaction pooler loses session-local state on the one-shot path #173/fix: keep bare [SET/CREATE TEMP, SELECT] batch on the shared client on a transaction pooler (#173) #174 — A bare batch (no session_id, no BEGIN) that sets session-local state earlier (a session SET or CREATE TEMP[ORARY] TABLE) then runs a result-set SELECT no longer silently loses that state on a pooler_mode = transaction connection. The rc.11 fix: pre-resolve column types on batch/session pooler path (#169) #172 fix routed the SELECT to a fresh one-shot that never saw the SET/temp table; the fix keeps the SELECT on the shared batch client with a pre-resolve, restoring main's within-batch guarantee (handles GLOBAL/LOCAL TEMP; excludes SET LOCAL / SET TRANSACTION / SET CONSTRAINTS).
• Worker pool starvation: stuck queries block ping/connect for every connection #167/fix: route ping/connect/cancel to dedicated lanes so stuck queries don't starve them (#167) #176 — A slow or hung query no longer starves ping/test_connection/initialize/shutdown and the cancel notification for every connection. RPCs are routed by method into three lanes before a worker pulls the line: a dedicated cancel lane (the relief valve, never queued behind the workers it relieves), a 2-worker lifecycle lane, and the existing 4-worker general lane; the SHUTDOWN_GRACE drain (Bug: Plugin process never exits after Tabularis quits if an RPC is in flight #155) covers all lanes' worker handles.

Known limitations (tracked as follow-ups, not regressions vs. the builtin):

• Bare [SET/CREATE TEMP, SELECT] batch on a real PgBouncer still loses session state — and can hang on non-builtin column types #175 — A bare [SET, SELECT] / [CREATE TEMP TABLE, SELECT] batch on a real PgBouncer (pool_mode = transaction) can still lose session state between autocommit statements and, in rare cases with non-builtin types under reassignment during the pre-resolve prepare, can hang. Wrap such batches in BEGIN/COMMIT; the direct + pooler_mode=transaction flag config (the common use) is unaffected.
• Stale composite type cache after ALTER TYPE on a recycled pooled connection #171 — A composite type ALTER TYPE-ed (same OID, new field layout) on a recycled pooled connection can read a stale cached Type and produce wrong JSON for the composite's fields. Pre-existing (a tokio-postgres/deadpool cache-invalidation limitation); the rc.11/fix: pre-resolve column types on direct connections to stop enum-table hang (#166) #168 pre-resolve widened the cache-warming window but did not introduce the bug.

Verification

• 441 unit tests pass; cargo clippy --all-targets -- -D warnings clean; markdownlint clean on CHANGELOG.md.
• The Bug: Regression in plugin v1.0.0-rc.10 table hangs while opening but works in v1.0.0-rc.8 #160→Bare [SET/CREATE TEMP, SELECT] batch on a transaction pooler loses session-local state on the one-shot path #173 fix chain was verified end-to-end against a live PostgreSQL (13/13 client_live_tests, 3/3 tests/shutdown.rs for Bug: Plugin process never exits after Tabularis quits if an RPC is in flight #155, 2/2 tests/worker_starvation.rs for Worker pool starvation: stuck queries block ping/connect for every connection #167, 38/39 tests/live_db with the 1 failure being the pre-existing pgvector fixture gap) in PRs fix: keep bare [SET/CREATE TEMP, SELECT] batch on the shared client on a transaction pooler (#173) #174/fix: route ping/connect/cancel to dedicated lanes so stuck queries don't starve them (#167) #176.

Follow-ups filed: #170 (direct-path .ok() swallow / timeout asymmetry), #171 (stale composite type cache), #175 (real-PgBouncer bare-batch), #177 (server-ignores-cancel worker-abort).

[kilo-code-bot]

Kilo Code Review could not run — your account is out of credits.

Add credits or switch to a free model to enable reviews on this change.