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 <tgl@xxxxxxxxxxxxx> Sent: Thursday, April 02, 2020 7:40 PM To: Abraham, Danny <danny_abraham@xxxxxxx> Cc: pgsql-general@xxxxxxxxxxxxxx Subject: [EXTERNAL] Re: too many clients already "Abraham, Danny" <danny_abraham@xxxxxxx> writes: > Well, I guess the questions is - how do I optimize PG for a stream of very short life checks... You should be using a connection pooler for a load like that. PG backends are fairly heavyweight things --- you don't want to fire one up for just a single query, at least not when there are many such queries per second. I think pgbouncer and pgpool are the most widely used options, but this is a bit outside my expertise. regards, tom lane
