MIME-Version: 1.0
References: <CAKgGyB_OmPnsgrr7YWOY=w8VDH7pN2hCt4Tsd1nJy=-xM=64eA@mail.gmail.com>
 <6b3cf69fa569d263a593cc2afe74dc35d29754eb.camel@cybertec.at>
In-Reply-To: <6b3cf69fa569d263a593cc2afe74dc35d29754eb.camel@cybertec.at>
From: KK CHN <kkchn.in@gmail.com>
Date: Fri, 10 Apr 2026 12:37:22 +0530
Message-ID: <CAKgGyB_zeOcCu+U=_=1OW_iJTcBweX1crEJQfxT-dN-b1_0JdQ@mail.gmail.com>
Subject: Re: Pgbouncer and Node JS application Query read timeout error
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000006ef34d064f15af2c"
Archived-At: <https://www.postgresql.org/message-id/CAKgGyB_zeOcCu%2BU%3D_%3D1OW_iJTcBweX1crEJQfxT-dN-b1_0JdQ%40mail.gmail.com>
Precedence: bulk

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

On Wed, Apr 8, 2026 at 11:58=E2=80=AFAM Laurenz Albe <laurenz.albe@cybertec=
.at>
wrote:

> On Wed, 2026-04-08 at 10:51 +0530, KK CHN wrote:
> > List, I am using pgbouncer(PgBouncer 1.23.1 RHEL 9.4) along with
> Postgres16(RHEL 9.4)
> > for connection pooling.
> >
> > Running a nodejs application which is throwing some errors  related to
> query timeout
> > which the development team suspect after pgbouncer deployment
> this behaviour appears,
> > but not sure
> >
> > The error which is thrown from  the nodejs logs as follows..
> >
> > [image showing an error "Query read timeout"]
> >
> > Is this due to   pgbouncer config issues or   nodejs  pool config issue=
s
> ?
> >
> > for  reference here the pgbouncer  config params and  node js  params a=
t
> present.
> >
> > pgbouncer.ini
> >
> > [...]
> > [pgbouncer]
> > pool_mode =3D transaction
> > default_pool_size =3D 50
> > min_pool_size =3D 30
> > reserve_pool_size =3D 10
> > reserve_pool_timeout =3D 5
> > max_db_connections =3D 130
> > max_user_connections =3D 180
> > server_lifetime =3D 3600
> > server_idle_timeout =3D 600
> > [...]
>
>
> The only way I can imagine that pgBouncer is leading to timeouts on the
> client side
> is if client sessions are waiting, because all connections are in use.
>
> You can run SHOW POOLS in the pgBouncer console to see if there are any
> "cl_waiting".
> If that is the case, you should configure the Node.js pools smaller, so
> that no
> connection has to wait.
>

Configuring Node.js  pools smaller ?  I couldn't get the  logic here  why
advised to reduce the pool size ?

Increasing pool size  more than 10 adversely affects the connection
establishment from Node.js  application ?          Since DB  is having
 Pgbouncer infront and   default_pool_size =3D 50 there ,  don't we have th=
e
freedom to increase node.js application pool size and it will help the
query timeout ?   or any hidden facts involved could you elaborate ..


Thank you,
Krishane


>
> Yours,
> Laurenz Albe
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Apr 8, =
2026 at 11:58=E2=80=AFAM Laurenz Albe &lt;<a href=3D"mailto:laurenz.albe@cy=
bertec.at">laurenz.albe@cybertec.at</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">On Wed, 2026-04-08 at 10:51 +0530, KK CH=
N wrote:<br>
&gt; List,=C2=A0I am using pgbouncer(PgBouncer 1.23.1 RHEL 9.4) along with=
=C2=A0 Postgres16(RHEL 9.4)<br>
&gt; for connection pooling.=C2=A0 =C2=A0<br>
&gt; <br>
&gt; Running a nodejs application which is throwing some errors=C2=A0 relat=
ed to query timeout<br>
&gt; which the development team suspect after pgbouncer deployment this=C2=
=A0behaviour appears,<br>
&gt; but not sure=C2=A0<br>
&gt; <br>
&gt; The error which is thrown from=C2=A0 the nodejs logs as follows..=C2=
=A0<br>
&gt; <br>
&gt; [image showing an error &quot;Query read timeout&quot;]<br>
&gt;<br>
&gt; Is this due to=C2=A0 =C2=A0pgbouncer config issues or=C2=A0 =C2=A0node=
js=C2=A0 pool config issues ?<br>
&gt; <br>
&gt; for=C2=A0 reference here the pgbouncer=C2=A0 config params and=C2=A0 n=
ode js=C2=A0 params at present.<br>
&gt; <br>
&gt; pgbouncer.ini<br>
&gt; <br>
&gt; [...]<br>
&gt; [pgbouncer]<br>
&gt; pool_mode =3D transaction<br>
&gt; default_pool_size =3D 50<br>
&gt; min_pool_size =3D 30<br>
&gt; reserve_pool_size =3D 10<br>
&gt; reserve_pool_timeout =3D 5<br>
&gt; max_db_connections =3D 130<br>
&gt; max_user_connections =3D 180<br>
&gt; server_lifetime =3D 3600<br>
&gt; server_idle_timeout =3D 600<br>
&gt; [...]<br>
<br>
<br>
The only way I can imagine that pgBouncer is leading to timeouts on the cli=
ent side<br>
is if client sessions are waiting, because all connections are in use.<br>
<br>
You can run SHOW POOLS in the pgBouncer console to see if there are any &qu=
ot;cl_waiting&quot;.<br>
If that is the case, you should configure the Node.js pools smaller, so tha=
t no<br>
connection has to wait.<br></blockquote><div><br></div><div>Configuring Nod=
e.js=C2=A0 pools smaller ?=C2=A0 I couldn&#39;t get the=C2=A0 logic here=C2=
=A0 why advised to reduce the pool size ?=C2=A0</div><div>=C2=A0</div><div>=
Increasing pool size=C2=A0 more than 10 adversely=C2=A0affects the connecti=
on=C2=A0 establishment from Node.js=C2=A0 application=C2=A0?=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Since DB=C2=A0 is having=C2=A0 =C2=A0Pgbouncer infront=
=C2=A0and=C2=A0 =C2=A0default_pool_size =3D 50 there ,=C2=A0 don&#39;t we h=
ave the freedom to increase node.js application pool size and it will help =
the query timeout ?=C2=A0 =C2=A0or any hidden facts involved could you elab=
orate ..</div><div><br></div><div><br></div><div>Thank you,</div><div>Krish=
ane</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">
<br>
Yours,<br>
Laurenz Albe<br>
</blockquote></div></div>

--0000000000006ef34d064f15af2c--