Message-ID: <27d9f616f9b94cef2932348b15c0ad80cb4c09c5.camel@cybertec.at>
Subject: Re: Pgbouncer
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Raj <rajeshkumar.dba09@gmail.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Thu, 14 May 2026 23:35:46 +0200
In-Reply-To: 
 <CAJk5Ata6-cjGenCxEyG2rTARNS6ETovWMX8SZYVvrDBtchSOXA@mail.gmail.com>
References: 
	<CAJk5Ata6-cjGenCxEyG2rTARNS6ETovWMX8SZYVvrDBtchSOXA@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/27d9f616f9b94cef2932348b15c0ad80cb4c09c5.camel%40cybertec.at>
Precedence: bulk

On Thu, 2026-05-14 at 17:49 +0530, Raj wrote:
> App team using connection pooling and opening 500 sessions which seems to=
 me stay ,
>=20
> In this case pgbouncer session pooling or transaction pooling which is be=
tter?

Transaction pooling.

> Max_connections in db: 1000
>=20
> Pool_mode=3Dsession
> Max connections in pgbouncer: 3000
> Default_pool_size=3D500
> Reserve_pool_size=3D100
> Min_pool_size=3D20

Too big. Set default_pool_size =3D min_pool_size =3D 20, and set reserve_po=
ol_size =3D 0.
If that turns out to be too small, increase slightly.

Yours,
Laurenz Albe