postgres · Issues· 303 open

fetch_types: false, deadlocks reserve() and alternatively pulls ~10KB from server before any work and can burn GBs of egress per month

invalid query results: rows count not cleared after partially streamed query fails on the same connection

sql.begin() resolves when COMMIT returns ROLLBACK after a caught savepoint failure

Disconnected transaction handles can read another user's rows through RLS

Configure a minimum connection pool size

Calling sql.end() or sql.close() after a server disconnection causes a permanent hang

Cloudflare build: a failed TLS handshake (untrusted CA, e.g. Supabase) surfaces as CONNECT_TIMEOUT instead of the real error

Failed connection establishment retries with no backoff and stampedes the whole pool (pathological against proxied/serverless Postgres)

nextWrite() throws an uncaughtException when a reserved connection's backend dies

sql.begin() always throws UNSAFE_TRANSACTION when max_pipeline is 0

arbitrary UNSAFE_TRANSACTION errors when using sql.begin

Unhandled rejection kills the process when the internal array-types query is cancelled (57014) - repro for #279

Connection of one in-process transaction being handed to a separate transaction, causing corruption

Cloudflare/workerd: sql.reserve() never resolves on a pool that has not yet opened a connection

Cloudflare/workerd: every sql.end() leaves an unhandled rejection (Stream was cancelled)