Re: LOG: unexpected EOF on client connection

On Sat, Oct 9, 2010 at 5:45 PM, Ben Carbery <ben(dot)carbery(at)gmail(dot)com> wrote:
>
>> Or that OP has a networking issue.  Some firewalls are known for
>> dropping what they think are idle connections when they aren't.
>>
>
> I don't think so.. EOF is an explicit termination, not a timeout as would
> caused by a firewall dropping traffic. It's more like what happens when the
> remote process on the client is killed for example. Postgres probably
> expects to see some kind of "quit" command prior to receiving the EOF.

Well, this is exactly the error I used to get when the problem was
having a firewall timeout between client and server at my last job.
The fix there was to play with the tcp_keepalive settings

--
To understand recursion, one must first understand recursion.