Re: SSL SYSCALL error: A blocking operation was interrupted by a call to WSACancelBlockingCall - Mailing list pgsql-general

From Tom Lane
Subject Re: SSL SYSCALL error: A blocking operation was interrupted by a call to WSACancelBlockingCall
Date
Msg-id 8046.1209651533@sss.pgh.pa.us
Whole thread Raw
In response to SSL SYSCALL error: A blocking operation was interrupted by a call to WSACancelBlockingCall  ("vyang" <vyang@apt-cafm.com>)
Responses Re: SSL SYSCALL error: A blocking operation was interrupted by a call to WSACancelBlockingCall  (Magnus Hagander <magnus@hagander.net>)
List pgsql-general
"vyang" <vyang@apt-cafm.com> writes:
> I'm having trouble with postgres filling the log with SSL SYSCALL error: A
> blocking operation was interrupted by a call to WSACancelBlockingCall.

That was fixed some time ago:

2007-05-17 21:20  tgl

    * src/backend/libpq/: be-secure.c (REL7_4_STABLE), be-secure.c
    (REL8_1_STABLE), be-secure.c (REL8_0_STABLE), be-secure.c
    (REL8_2_STABLE), be-secure.c: Remove redundant logging of send
    failures when SSL is in use.  While pqcomm.c had been taught not to
    do that ages ago, the SSL code was helpfully bleating anyway.
    Resolves some recent reports such as bug #3266; however the
    underlying cause of the related bug #2829 is still unclear.

Update to a newer release.

            regards, tom lane

pgsql-general by date:

Previous
From: Jeremy Harris
Date:
Subject: Re: inheritance. more.
Next
From: "Osvaldo Kussama"
Date:
Subject: Re: question about join