Message-ID: <6b3cf69fa569d263a593cc2afe74dc35d29754eb.camel@cybertec.at>
Subject: Re: Pgbouncer and Node JS application Query read timeout error
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: KK CHN <kkchn.in@gmail.com>, pgsql-general <pgsql-general@postgresql.org>
Date: Wed, 08 Apr 2026 08:27:59 +0200
In-Reply-To: <CAKgGyB_OmPnsgrr7YWOY=w8VDH7pN2hCt4Tsd1nJy=-xM=64eA@mail.gmail.com>
References: 
	<CAKgGyB_OmPnsgrr7YWOY=w8VDH7pN2hCt4Tsd1nJy=-xM=64eA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/6b3cf69fa569d263a593cc2afe74dc35d29754eb.camel%40cybertec.at>
Precedence: bulk

On Wed, 2026-04-08 at 10:51 +0530, KK CHN wrote:
> List,=C2=A0I am using pgbouncer(PgBouncer 1.23.1 RHEL 9.4) along with=C2=
=A0 Postgres16(RHEL 9.4)
> for connection pooling.=C2=A0 =C2=A0
>=20
> Running a nodejs application which is throwing some errors=C2=A0 related =
to query timeout
> which the development team suspect after pgbouncer deployment this=C2=A0b=
ehaviour appears,
> but not sure=C2=A0
>=20
> The error which is thrown from=C2=A0 the nodejs logs as follows..=C2=A0
>=20
> [image showing an error "Query read timeout"]
>
> Is this due to=C2=A0 =C2=A0pgbouncer config issues or=C2=A0 =C2=A0nodejs=
=C2=A0 pool config issues ?
>=20
> for=C2=A0 reference here the pgbouncer=C2=A0 config params and=C2=A0 node=
 js=C2=A0 params at present.
>=20
> pgbouncer.ini
>=20
> [...]
> [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 cli=
ent 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 tha=
t no
connection has to wait.

Yours,
Laurenz Albe