From: | Mark Rostron <mrostron(at)ql2(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Samir Bhakta <sbhakta(at)ql2(dot)com> |
Subject: | db server processes hanging around |
Date: | 2012-06-19 16:29:19 |
Message-ID: | CAE=WP0qu2KMA1vJup8A4wAhsKKHUNL=6EfqRmaV+MrOiMM_Ngg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
hi
we are running out of database connections.
we are using pg 9.0.6 on linux centos 5.7 64bit.
we are not using any go-between connection pools such as pgbouncer or
pgpool - connections occur directly from client to database.
the connection setup on the client (java) is default, only providing
(user,password,dbhost,dbname).
we have about 10 developers developing java thru IDEA who start/stop the
local tomcat server frequently.
i have observed that tomcat doesn't disconnect from pg cleanly when they
cycle, and the server processes persist for a long time.
I have had them reduce their local connection factory pool size to 1 (this
helped) and increased our max_connection value to 1000.
yet the problem persists.
I have noticed that the server processes do die "after some time" - due to
inactivity?
we are looking for a way to control server processes better than we are
doing now.
thnx for your time.
mr
From | Date | Subject | |
---|---|---|---|
Next Message | McKay | 2012-06-19 17:01:47 | Re: bytea insert difference between 8.3 and 9.x |
Previous Message | Greg Sabino Mullane | 2012-06-19 15:49:39 | Re: Feature discussion: Should syntax errors abort a transaction? |