From: Rachel Greenham <rachel@enlarion.demon.co.uk>
To: pgsql-interfaces@postgresql.org
Subject: JDBC problem - again
Date: Mon, 26 Jul 1999 09:35:50 +0100
Message-ID: <379C1DE6.7FAE7173@enlarion.demon.co.uk> (raw)
Peter, did you ever get around to ensuring a closed connection when a
Connection object is finalised? I've just hit the problem again, with
Postgres dying of too many open connections. I thought I'd fixed it on
my client code by always closing the Connections before they go out of
scope, but evidently not, one is hiding somewhere taking about a
fortnight to happen enough to kill Postgres, and it's going to be a
bitch to track down - and I really can't see the harm in the connection
being closed on finalise.
--
Rachel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: rachel@enlarion.demon.co.uk
Subject: Re: JDBC problem - again
In-Reply-To: <379C1DE6.7FAE7173@enlarion.demon.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox