| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, DrakoRod <drakoflames(at)hotmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting |
| Date: | 2017-06-27 23:04:00 |
| Message-ID: | CAKFQuwZbZ10RuCNoJpvt7g2vAi9RLcpeodcmrUeXrCXe+Q+f9g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jun 27, 2017 at 3:41 PM, Melvin Davidson <melvin6925(at)gmail(dot)com>
wrote:
> *His problem is NOT 'idle in transaction' per se. It is all connections
> are used up.*
> *Hence the need for pg_bouncer for connection pooling.*
>
>
Whether pg_bouncer provides a viable solution is just as big an unknown as
whether "idle in transaction" is the biggest contributor to the problem.
If all of them are idle in transaction then pg_bouncer is powerless to
help. If they are generally just long-lived sessions and only a few stay
in transaction then transaction pooling mode may help.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | DrakoRod | 2017-06-27 23:16:53 | Re: postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting |
| Previous Message | Adrian Klaver | 2017-06-27 23:01:17 | Re: postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting |