public inbox for [email protected]
help / color / mirror / Atom feedFrom: Durgamahesh Manne <[email protected]>
To: pgsql-general <[email protected]>
Subject: pgbouncer transaction pool mode issue for prepared statements
Date: Mon, 16 Feb 2026 18:54:44 +0530
Message-ID: <CAJCZkoJr=Az5PMDj15O5ekzK+vK454WzoWZdQ9XUfTkTWtCQGw@mail.gmail.com> (raw)
Hi PGDG Team
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.
Regards
Durga Mahesh
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: pgbouncer transaction pool mode issue for prepared statements
In-Reply-To: <CAJCZkoJr=Az5PMDj15O5ekzK+vK454WzoWZdQ9XUfTkTWtCQGw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox