Re: postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Melvin Davidson <melvin6925(at)gmail(dot)com>
Cc: 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:01:17
Message-ID: fd1eb50a-6f76-745b-9a49-ca34615b87ae@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 06/27/2017 03:41 PM, Melvin Davidson wrote:
>
>
> On Tue, Jun 27, 2017 at 6:32 PM, Adrian Klaver

> *His problem is NOT 'idle in transaction' per se. It is all connections
> are used up.*

Not following. The 'idle in transaction' queries are coming in through a
connection so having them around is keeping a connection open. Dealing
with them will help with the connection count. Using pg_bouncer is an
option, but if you have a process that is not properly closing
transactions/connections you could get into an arms race between that
process and the size of your connection pool.

> *Hence the need for pg_bouncer for connection pooling.*
> --
> *Melvin Davidson*

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2017-06-27 23:04:00 Re: postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting
Previous Message PT 2017-06-27 22:57:57 Re: postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting