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.kla...@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
