# X_DB_STATEMENT_BOUND_LOST

## Means

the session's statement bound is not the role's

## Typical cause

logged at boot and reported by x doctor, never a refusal: statement_timeout or idle_in_transaction_session_timeout as the session reads it differs from POOL_PROFILES, or is 0 with DATABASE_POOLER set. A pooler that ignores or drops libpq options does this silently

## Fix

`psql "<DATABASE_URL without its options parameter>" -c "alter role <user> set statement_timeout = '10s'" -c "alter role <user> set idle_in_transaction_session_timeout = '30s'"`, then reopen the pooler's server connections; or `export DATABASE_POOLER=transaction` if a pooler sits in the path. The error's own `fix:` cuts the parameter with `sed`

[Entity and database](/error-codes#entity-and-database)