Subject: Re: PostgreSQL(v9.6.5) not releasing old/inactive IDLE connections
To: pgsql-admin@lists.postgresql.org
References: 
 <OS3PR01MB581659FF3F8020F174751B4BA76F9@OS3PR01MB5816.jpnprd01.prod.outlook.com>
 <c0ed0cc7-1212-c34c-65ab-139936bdf785@pscs.co.uk>
From: Thomas Kellerer <shammat@gmx.net>
Message-ID: <da132b1a-a3b1-cd67-87bc-e05d143587e1@gmx.net>
Date: Wed, 8 Dec 2021 12:24:46 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23)
 Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
In-Reply-To: <c0ed0cc7-1212-c34c-65ab-139936bdf785@pscs.co.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/da132b1a-a3b1-cd67-87bc-e05d143587e1%40gmx.net>
Precedence: bulk

Paul Smith schrieb am 08.12.2021 um 10:18:
>> I'm facing "Too many clients already" error frequently with my
>> PostgreSQL (v9.6.5) container (i.e. being used along with CKAN
>> application i.e. A open source data management system
>> <https://ckan.org/> ), I have observed that PostgreSQL is not
>> releasing IDLE connections from their end. I have set
>> "max_connetions =3D 100" in postgresql.
>>
> It is the responsibility of the client software to release
> connections when they are no longer needed. The server won't just
> time-out idle connections unless it is told to do so

Automatically closing idle sessions is only available since Postgres 14