Re: connection trouble - Mailing list pgsql-novice

From Tom Lane
Subject Re: connection trouble
Date
Msg-id 22389.1123772387@sss.pgh.pa.us
Whole thread Raw
In response to Re: connection trouble  (Vanessa Conchodon <v.conchodon@smie.com>)
Responses Re: connection trouble
List pgsql-novice
Vanessa Conchodon <v.conchodon@smie.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

pgsql-novice by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: passing column name to a PL/pgsql function for ALTER TABLE ADD
Next
From: Tom Lane
Date:
Subject: Re: Forcing WAL switch