Re: too many clients already

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Abraham, Danny" <danny_abraham(at)bmc(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: too many clients already
Date: 2020-04-02 16:40:22
Message-ID: 20255.1585845622@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Abraham, Danny" <danny_abraham(at)bmc(dot)com> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Abraham, Danny 2020-04-02 17:13:58 RE: Re: too many clients already
Previous Message Abraham, Danny 2020-04-02 16:20:27 RE: Re: too many clients already