| From: | Abdul Qoyyuum <aqoyyuum(at)cardaccess(dot)com(dot)au> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Is it normal to have too many idle processes in postgresql cluster? |
| Date: | 2021-03-08 06:41:25 |
| Message-ID: | CAA3DN=VeRTh8ETD2Hh=CP2soSo3hLge0nhT1cpTF583mWr-8rw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks Christophe! I guess I had nothing to be worried about.
On Mon, Mar 8, 2021 at 9:46 AM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
> > On Mar 7, 2021, at 17:34, Abdul Qoyyuum <aqoyyuum(at)cardaccess(dot)com(dot)au>
> wrote:
> > Seems to get me worried. Should I be worried? Is this normal? If not,
> what should I do?
>
> It's normal. Every connected client has an associated backend process,
> even if the client isn't doing anything. That's what the "idle" state
> means. You can consider using a pooler such as pgbouncer to reduce the
> number of connections the clients have open, although 200 open connections
> is nothing concerning.
>
> --
> -- Christophe Pettus
> xof(at)thebuild(dot)com
>
>
--
Abdul Qoyyuum Bin Haji Abdul Kadir
HP No: +673 720 8043
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daisuke Ikeda | 2021-03-08 13:30:04 | PostgreSQL container crash trouble. |
| Previous Message | Christophe Pettus | 2021-03-08 01:46:50 | Re: Is it normal to have too many idle processes in postgresql cluster? |