On 2-Dec-06, at 6:27 AM, Martijn van Oosterhout wrote:
On Fri, Dec 01, 2006 at 08:26:53PM -0700, Brian Wipf wrote:
Now I know the cause at least. If anyone has an idea on how to kill a
similar hung connection without rebooting the server, I would
appreciate any suggestions.
I'm unsure about wh
On Fri, Dec 01, 2006 at 08:26:53PM -0700, Brian Wipf wrote:
> Now I know the cause at least. If anyone has an idea on how to kill a
> similar hung connection without rebooting the server, I would
> appreciate any suggestions.
I'm unsure about why it wouldn't respond to a sigint, but did you tr
I finally reboot the client server. It took a couple of minutes after
that, but the hung connection did go away on the server.
I found a similar cause to my problem in the archives:
http://archives.postgresql.org/pgsql-jdbc/2005-05/msg00044.php
In order for the PostgreSQL JDBC adaptor to not f
Based on the backend_start time in pg_stat_activity, I was able to
find the problem query in our logs. The query is a simple one, but
returns a lot of results for a report. This was the error in the logs:
org.postgresql.util.PSQLException: Ran out of memory retrieving query
results.
