MIME-Version: 1.0
References: <CAJCZkoJr=Az5PMDj15O5ekzK+vK454WzoWZdQ9XUfTkTWtCQGw@mail.gmail.com>
 <8c5e13fc-43a2-4739-bc87-d1f664cdb6ed@aklaver.com>
In-Reply-To: <8c5e13fc-43a2-4739-bc87-d1f664cdb6ed@aklaver.com>
From: Durgamahesh Manne <maheshpostgres9@gmail.com>
Date: Tue, 17 Feb 2026 00:40:08 +0530
Message-ID: <CAJCZkoK1jumhXJWbmZfmPcgQaBZcU8paBf-RyZTSMCHAeprZUQ@mail.gmail.com>
Subject: Re: pgbouncer transaction pool mode issue for prepared statements
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000b849fb064af5b405"
Archived-At: <https://www.postgresql.org/message-id/CAJCZkoK1jumhXJWbmZfmPcgQaBZcU8paBf-RyZTSMCHAeprZUQ%40mail.gmail.com>
Precedence: bulk

--000000000000b849fb064af5b405
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 16 Feb, 2026, 21:35 Adrian Klaver, <adrian.klaver@aklaver.com>
wrote:

> On 2/16/26 05:24, Durgamahesh Manne wrote:
> > Hi PGDG Team
> >
> >
> >
> > We=E2=80=99re currently facing an issue with PgBouncer transaction pool=
ing 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 hav=
e
> > a very high number of connections that we cannot fully control.
> > Environment details: PgBouncer version: 1.25.1 PostgreSQL version: 16.1=
1
> >
> >   The specific error we=E2=80=99re 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=E2=80=91=
level
> > changes? Any guidance or solutions would be greatly appreciated.
>
> A little exploration/searching would have revealed:
>
> https://www.pgbouncer.org/faq.html
>
> 5), How to use prepared statements with transaction pooling?
>
> Which leads to:
>
>
> https://www.pgbouncer.org/faq.html#how-to-use-prepared-statements-with-tr=
ansaction-pooling
>
> which in turn leads to:
>
> https://www.pgbouncer.org/config.html#max_prepared_statements
>
> Note though the caveat in last link:
>
> "Note: This tracking and rewriting of prepared statement commands does
> not work for SQL-level prepared statement commands, so PREPARE, EXECUTE
> and DEALLOCATE are forwarded straight to Postgres. The exception to this
> rule are the DEALLOCATE ALL and DISCARD ALL commands, these do work as
> expected and will clear the prepared statements that PgBouncer tracked
> for the client that sends this command."
>
>
> >
> > Regards
> > Durga Mahesh
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com


Hi

Thank you so much for this information

Regards
Durga Mahesh

>
>

--000000000000b849fb064af5b405
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote gmail_quote_contai=
ner"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, 16 Feb, 2026, 21:35 Adri=
an Klaver, &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adrian.klaver@a=
klaver.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2/16/=
26 05:24, Durgamahesh Manne wrote:<br>
&gt; Hi PGDG Team<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; We=E2=80=99re currently facing an issue with PgBouncer transaction poo=
ling mode, <br>
&gt; where prepared statements are failing, and we are unable to modify the=
 <br>
&gt; application code to disable or change how prepared statements are used=
.<br>
&gt; <br>
&gt; Switching to session pooling mode is not feasible for us because we ha=
ve <br>
&gt; a very high number of connections that we cannot fully control. <br>
&gt; Environment details: PgBouncer version: 1.25.1 PostgreSQL version: 16.=
11<br>
&gt; <br>
&gt;=C2=A0 =C2=A0The specific error we=E2=80=99re seeing is:<br>
&gt; <br>
&gt; bind message has 43 result formats but query has 47 columns<br>
&gt; <br>
&gt; ERROR: unnamed prepared statement does not exist Repeatedly logs<br>
&gt; <br>
&gt;=C2=A0 =C2=A0Has anyone encountered this issue with transaction pooling=
 and <br>
&gt; prepared statements? Are there any PgBouncer parameters or settings we=
 <br>
&gt; can use to mitigate this problem without requiring application=E2=80=
=91level <br>
&gt; changes? Any guidance or solutions would be greatly appreciated.<br>
<br>
A little exploration/searching would have revealed:<br>
<br>
<a href=3D"https://www.pgbouncer.org/faq.html" rel=3D"noreferrer noreferrer=
" target=3D"_blank">https://www.pgbouncer.org/faq.html</a><br>
<br>
5), How to use prepared statements with transaction pooling?<br>
<br>
Which leads to:<br>
<br>
<a href=3D"https://www.pgbouncer.org/faq.html#how-to-use-prepared-statement=
s-with-transaction-pooling" rel=3D"noreferrer noreferrer" target=3D"_blank"=
>https://www.pgbouncer.org/faq.html#how-to-use-prepared-statements-with-tra=
nsaction-pooling</a><br>
<br>
which in turn leads to:<br>
<br>
<a href=3D"https://www.pgbouncer.org/config.html#max_prepared_statements" r=
el=3D"noreferrer noreferrer" target=3D"_blank">https://www.pgbouncer.org/co=
nfig.html#max_prepared_statements</a><br>
<br>
Note though the caveat in last link:<br>
<br>
&quot;Note: This tracking and rewriting of prepared statement commands does=
 <br>
not work for SQL-level prepared statement commands, so PREPARE, EXECUTE <br=
>
and DEALLOCATE are forwarded straight to Postgres. The exception to this <b=
r>
rule are the DEALLOCATE ALL and DISCARD ALL commands, these do work as <br>
expected and will clear the prepared statements that PgBouncer tracked <br>
for the client that sends this command.&quot;<br>
<br>
<br>
&gt; <br>
&gt; Regards<br>
&gt; Durga Mahesh<br>
<br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank" rel=3D"noref=
errer">adrian.klaver@aklaver.com</a></blockquote></div></div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Hi</div><div dir=3D"auto"><br></div><div di=
r=3D"auto">Thank you so much for this information=C2=A0</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Regards</div><div dir=3D"auto">Durga Mahesh=
</div><div dir=3D"auto"><div class=3D"gmail_quote gmail_quote_container"><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><br>
</blockquote></div></div></div>

--000000000000b849fb064af5b405--