We have a recurrent problem with our PostgreSQL server (v.8.2): some of our web site applications are creating a lot of connections to a lot of our database (a little bit more than 60).
We already adapted the maximum PostgreSQL connections (200), but it's seams not enough as we have an error message saying that the numbers of connections limit has been reached.
Sometimes, the w3wp.exe process (from IIS) is using more than 80% of the CPU calculation time.
As we supposed that those problems are more or less linked. We have have found the the connections/PostgreSQL Windows processes sometimes run nor one hour after the last access. How should we solve this problem?