Big installation: max_connections is 1200, shared_buffers is 2GB
-----Original Message-----
From: Adrian Klaver <adrian.klaver@aklaver.com>
Sent: Thursday, April 02, 2020 6:30 PM
To: Abraham, Danny <danny_abraham@bmc.com>; pgsql-general@postgresql.org
Subject: [EXTERNAL] Re: too many clients already
On 4/2/20 8:22 AM, Abraham, Danny wrote:
> No pg-bouncer or connection pooling.
> ps -elf | grep postgres | grep idle | wc -l ==> 61
>
> and BTW: Running, say 500 one command psql in parallel will have the same affect..
Hmm. In psql on the cluster in question what does below return?:
show max_connections;
>
> -----Original Message-----
> From: Rob Sargent <robjsargent@gmail.com>
> Sent: Thursday, April 02, 2020 6:10 PM
> To: Abraham, Danny <danny_abraham@bmc.com>
> Cc: pgsql-general@postgresql.org
> Subject: [EXTERNAL] Re: too many clients already
>
>
>
>> On Apr 2, 2020, at 9:06 AM, Abraham, Danny <danny_abraham@bmc.com> wrote:
>>
>> Hi,
>>
>> Will appreciate a hint here.
>>
>> Running on a big and stressed AIX platform and receiving lots of "CDTFATAL: sorry, too many clients already"
>> and transient difficulty to log in.
>>
>> Happens on all PG versions (Tested 9.5,10.4,11.5)
>>
>> Big installation: max_connections is 1200, shared_buffers is 2GB
>>
>> But .. select count(*) from pg_stat_activity is only 66.
>>
>> Thanks
>>
>> Danny
>>
>>
> Lots of idle, kept-alive clients? Do you have a connection pooler (e.g. pg-bouncer)?
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com