Is there a way to remove idle connections? My postgres server is
getting serveral hundred idle connections. It's due to a postgres .NET
provider not closing the connections properly. I don't want to kill
them all, or restart postgres everytime the connections go crazy.
-Josh
On 19 Oct 2004 at 13:00, Josh Close wrote:
Is there a way to remove idle connections? My postgres server is
getting serveral hundred idle connections. It's due to a postgres .NET
provider not closing the connections properly. I don't want to kill
them all, or restart postgres everytime the
On Tue, 19 Oct 2004 19:24:23 +0100, Gary Doades [EMAIL PROTECTED] wrote:
I would have though it would be better to fix the client application. If the
app is not closing connections then you may be leaking handles and
memory.
What .NET provider is this? Are you sure it is not just normal
On 19 Oct 2004 at 13:32, Josh Close wrote:
The provider is corelabs. The programmer that wrote the code says he's
closing the connections, but they aren't actually closing.
Any ideas? Or better yet, do you know of a good postgres .net provider?
Hmm, I've had lots of problems with the
Josh Close wrote:
Is there a way to remove idle connections? My postgres server is
getting serveral hundred idle connections. It's due to a postgres .NET
provider not closing the connections properly. I don't want to kill
them all, or restart postgres everytime the connections go crazy.
I do not
