From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Vanessa Conchodon <v(dot)conchodon(at)smie(dot)com> |
Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: connection trouble |
Date: | 2005-08-11 14:59:47 |
Message-ID: | 22389.1123772387@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Vanessa Conchodon <v(dot)conchodon(at)smie(dot)com> writes:
> Michael Fuhr wrote:
>> On Thu, Aug 11, 2005 at 12:09:56PM +0200, Vanessa Conchodon wrote:
>>> I've got this message in the log of one of my software
>>> (message repeated every 3 minutes at least):
>>> "could not receive server response to SSL negotiation packet:
>>> Interrupted system call".
>>
>> What software are you using, what version of PostgreSQL, and on
>> what platform? PostgreSQL 7.3 and later should handle EINTR
>> (interrupted system call) so that you don't see this exact error
>> message.
> I'm using a 7.4.7-6sarge1 version on a debian sarge.
It's really, really, really hard to believe that 7.4 libpq would emit
this. The code looks like
retry_ssl_read:
nread = recv(conn->sock, &SSLok, 1, 0);
if (nread < 0)
{
if (SOCK_ERRNO == EINTR)
/* Interrupted system call - just try again */
goto retry_ssl_read;
printfPQExpBuffer(&conn->errorMessage,
libpq_gettext("could not receive server response to SSL negotiation packet: %s\n"),
SOCK_STRERROR(SOCK_ERRNO, sebuf, sizeof(sebuf)));
goto error_return;
}
Are you sure your application isn't linked to an older (7.2) libpq?
The EINTR test wasn't there in 7.2.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-08-11 15:03:55 | Re: Forcing WAL switch |
Previous Message | Bruce Momjian | 2005-08-11 14:53:29 | Re: Forcing WAL switch |