thanks for your feedback. While implementing connection pooling would make resources utilization more efficient, I don't think it's the root of my problem. Most of the connected clients are at IDLE. When I do
select * from pg_stat_activity where current_query not like '%IDLE%';
I only see several active queries at any given time.
-- Vlad
-- Vlad
On Wed, Nov 14, 2012 at 3:23 PM, John R Pierce <pierce@xxxxxxxxxxxx> wrote:
On 11/14/12 1:13 PM, Vlad wrote:thats a really high client connection count for a 8 core system.
Postgresql 9.1.6.
Postgres usually has 400-500 connected clients, most of them are idle.
Database is over 1000 tables (across 5 namespaces), taking ~150Gb on disk.
I'd consider implementing a connection pool (like pgbouncer), and rewriting your client applications to connect, do a transaction, disconnect, so the actual number of postgres connections is much lower, say in the 16-48 range.
