Is Your Rust Request Waiting for a Connection or for PostgreSQL?
Trace a Rust request from SQLx acquisition to PostgreSQL locks. Find long-held connections, release them during unrelated work, and keep stale quotes from being saved.
Rust and database failures
Start with the symptom you can observe. Each article explains a different boundary between the Rust application, database driver and database, with source code and checks for the result.
PostgreSQL Committed, but the Rust Caller Lost the Reply
Drop a PostgreSQL commit reply at a controlled protocol boundary. Recover with an operation key, an atomic receipt, and a replay that checks the original input.
A Slow Download Can Keep Your Rust Database Pool Busy
Follow PostgreSQL rows through a real HTTP download. See why a slow client can hold a SQLx connection, what bounded pages change, and what disconnect cleanup must release.
A SQLx Offline Build Can Pass With Stale Database Metadata
Change a PostgreSQL column from integer to bigint and compare offline compilation, runtime decoding, and a live macro check against the changed schema.
Your Rust Binary Built, but Oracle Client Is Missing in Deployment
Use a client-only initialization probe to separate an Oracle library loading failure from database authentication. Check architecture, loader paths, and the deployment artifact.
A Rust Timeout Can Leave PostgreSQL Work Running
Observe server work after a Rust timeout, then check statement budgets, failed transactions and timeout settings across reused SQLx connections.
A Bounded Rust Channel Does Not Bound Its Database Producers
Pause a consumer while several Rust tasks fetch database payloads. Count data retained outside a one-slot queue, then reserve a shared byte budget before fetching.