Re: Error on PQputline() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Error on PQputline()
Date
Msg-id 23432.1021679194@sss.pgh.pa.us
Whole thread Raw
In response to Re: Error on PQputline()  ("Dann Corbit" <DCorbit@connx.com>)
List pgsql-hackers
"Dann Corbit" <DCorbit@connx.com> writes:
>> I'm confused too.  For starters, I cannot find that error message
>> string about 'A non-blocking socket operation could not be completed
>> immediately' anywhere.  Got any idea what's producing that?  Exactly
>> which version of libpq are you using, anyway?

> 7.1.3.  Sorry for running on fossil PostgreSQL.

No such string in 7.1.3 either.

> printfPQExpBuffer(&conn->errorMessage,
>                       "pqFlush() --  couldn't send
> data: errno=%d\n%s\n",
> errno, strerror(errno));
>                     /* We don't assume it's a fatal
> error... */
>                     return EOF;
> /*
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ^^^^^^^
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!
> */

Unless your strerror is really weird, that message is only going to have
produced "pqFlush() --  couldn't send data: errno=0\nNo error\n".
The bit about a non-blocking socket could not have come from strerror
AFAICS; it hasn't got enough context to know that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Dann Corbit"
Date:
Subject: Re: Error on PQputline()
Next
From: Manuel Sugawara
Date:
Subject: Redhat 7.3 time manipulation bug