Jeff Wigal wrote:
>>> I am running Postgres 8.2.3 and am seeing the following error messages in my
>>> logs:
>>>
>>> LOG: SSL SYSCALL error: Connection reset by peer
>>> LOG: could not receive data from client: Connection reset by peer
>>> LOG: unexpected EOF on client connection
>>> LOG: could
I'm in the process of tracking down the cause of this... Is there any way on
the server side of things to terminate a connection after "x" number of
minutes? For what we're doing, there is no reason to have a connection open
after 10 minutes.
Thanks in advance--
On Tue, Apr 1, 2008 at 5:44 PM, J
That's possible. They are communicating with the server using MS Access,
which is connecting to the server through the Postgres ODBC driver.
On Tue, Apr 1, 2008 at 5:12 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Jeff Wigal (Referee Assistant)" <[EMAIL PROTECTED]> writes:
> > I am running Postgre
"Jeff Wigal (Referee Assistant)" <[EMAIL PROTECTED]> writes:
> I am running Postgres 8.2.3 and am seeing the following error messages in my
> logs:
> LOG: SSL SYSCALL error: Connection reset by peer
> LOG: could not receive data from client: Connection reset by peer
> LOG: unexpected EOF on cli
Much the same as this person here:
http://archives.postgresql.org/pgsql-general/2008-02/msg00689.php
I am running Postgres 8.2.3 and am seeing the following error messages in my
logs:
LOG: SSL SYSCALL error: Connection reset by peer
LOG: could not receive data from client: Connection reset by
That makes sense since the "connection reset by peer" statement is
always followed immediately by
"unexpected EOF on client connection"
I should have noticed that before :-0
Thanks!
On Apr 20, 2004, at 10:04 PM, Doug McNaught wrote:
Joe Lester <[EMAIL PROTECTED]> writes:
I'm seeing this mess
