Agree.
I suspect that this is a mal configured pgpool - the developer thinks that the
pool is reusing connections,
While it is, in fact, reopening them.
-Original Message-
From: Tom Lane
Sent: Thursday, April 02, 2020 7:40 PM
To: Abraham, Danny
Cc: pgsql-gene...@postgresql.org
Subject
Well, I guess the questions is - how do I optimize PG for a stream of very
short life checks...
See below:
2020-04-02 11:05:37.010 CDTLOG: connection received: host=10.64.72.157
port=45799
2020-04-02 11:05:37.014 CDTLOG: connection received: host=10.64.72.157
port=45814
2020-04-02 11:05:37.01
va-tlv-ctm-qa22.isr.bmc.com% sql
psql: FATAL: sorry, too many clients already
va-tlv-ctm-qa22.isr.bmc.com% sql
psql (11.5)
Type "help" for help.
ctrlmdb=> show max_connections;
max_connections
-
1200
(1 row)
ctrlmdb=> show shared_buffers;
shared_buffers
2000M
Big installation: max_connections is 1200, shared_buffers is 2GB
-Original Message-
From: Adrian Klaver
Sent: Thursday, April 02, 2020 6:30 PM
To: Abraham, Danny ; pgsql-gene...@postgresql.org
Subject: [EXTERNAL] Re: too many clients already
On 4/2/20 8:22 AM, Abraham, Danny wrote:
> N
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..
-Original Message-
From: Rob Sargent
Sent: Thursday, April 02, 2020 6:10 PM
To: Abraham, Danny
Cc: pgsql-gene.
