Date: Thu, 3 Oct 2013 07:14:24 -0700 (PDT)
From: David Johnston <polobo@yahoo.com>
To: pgsql-admin@postgresql.org
Message-ID: <1380809664829-5773234.post@n5.nabble.com>
In-Reply-To: <A7A2044B8A59DA4F9F07599B3B1CA1210E4CA0F7@MX101CL02.corp.emc.com>
References: <A7A2044B8A59DA4F9F07599B3B1CA1210E4CA0F7@MX101CL02.corp.emc.com>
Subject: Re: postgres connections in IDLE state..
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Rajagopalan, Jayashree wrote
> I'm seeing intermittently - the DB connections getting stale - and not
> getting returned to the Hibernate session pool. Some of the connections
> are as old as 9 days.

The whole point of a connection pool is to keep open connections to the
database.  These connections, when not in use, are "IDLE".  I would expect
to see a single connection for every permanent pool connection.

I don't see any problem with what you show and describe other than I'd
expect more than 2 idle connections and I'd expect the supposed "problem" to
be persistent.

In your example the backend has been alive and in the pool since 9/11 and
the most recent time it was used was 10/2.  In between those two dates there
were many other times the connection was used.

David J.


--
View this message in context: http://postgresql.1045698.n5.nabble.com/postgres-connections-in-IDLE-state-tp5773232p5773234.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin