Re: LOG: unexpected EOF on client connection - Mailing list pgsql-general

From Scott Marlowe
Subject Re: LOG: unexpected EOF on client connection
Date
Msg-id AANLkTins7zv_fSCar=kJW7hJBY391ifrp+rT4VZcBERv@mail.gmail.com
Whole thread Raw
In response to Re: LOG: unexpected EOF on client connection  (Ben Carbery <ben.carbery@gmail.com>)
List pgsql-general
On Sat, Oct 9, 2010 at 5:45 PM, Ben Carbery <ben.carbery@gmail.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.

pgsql-general by date:

Previous
From: Ben Carbery
Date:
Subject: Re: LOG: unexpected EOF on client connection
Next
From: Mike Christensen
Date:
Subject: Postgres won't start after setting ssl=on