We’re currently facing an issue with PgBouncer transaction pooling mode, where prepared statements are failing, and we are unable to modify the application code to disable or change how prepared statements are used.
Switching to session pooling mode is not feasible for us because we have a very high number of connections that we cannot fully control. Environment details: PgBouncer version: 1.25.1 PostgreSQL version: 16.11
The specific error we’re seeing is:
bind message has 43 result formats but query has 47 columns
ERROR: unnamed prepared statement does not exist Repeatedly logs
Has anyone encountered this issue with transaction pooling and prepared statements? Are there any PgBouncer parameters or settings we can use to mitigate this problem without requiring application‑level changes? Any guidance or solutions would be greatly appreciated.
