The following bug has been logged online:

Bug reference: 2570
Logged by: Pavel Golub
Email address: pavel (AT) microolap (DOT) com
PostgreSQL version: 8.0.x
Operating system: Windows XP
Description: Connection closed unexpectedly
Details:

Bug may be reproduced by any tool using libpq.dll, e.g. PgAdminIII.

1. Connect to server.
2. Execute some queries, e.g. SELECT 2;
3. Wait for a while (to be sure I suggest 20 minutes)
4. Try to execute query, e.g. SELECT version()

We got an error: "server closed the connection unexpectedly. This probably
means the server terminates abnormaly before or while processing the
request."

And we have sonnection status: "Connection broken".

Time of idle may vary, but the behavior is always the same.

No firewall. No additional network settings. Server and client on the same
machine (localhost).

I reproduced this on my machine many times, and have requests from my users.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

"Pavel Golub" <pavel (AT) microolap (DOT) com> writes:
[ shrug... ] You've got broken networking infrastructure. Postgres
itself does not have any connection timeout. (Some have complained
that this is a bug, but at least it lets us reject this type of
complaint as not our problem...)

If you were using 8.1 you might be able to stave off the connection
drop by reducing tcp_keepalives_idle, but I don't have any suggestions
for 8.0.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly