Re: BUG #16678: The ecpg connect/test5 test sometimes fails on Windows - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16678: The ecpg connect/test5 test sometimes fails on Windows
Date
Msg-id 383222.1603561145@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #16678: The ecpg connect/test5 test sometimes fails on Windows  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: BUG #16678: The ecpg connect/test5 test sometimes fails on Windows  (Alexander Lakhin <exclusion@gmail.com>)
List pgsql-bugs
Alexander Lakhin <exclusion@gmail.com> writes:
> So I've also tested on Windows the following version:
>         secure_close(MyProcPort);
>         shutdown(MyProcPort->sock, SD_SEND);
>         for(;;) {
>             char buffer[1000];
>             int res = recv(MyProcPort->sock, buffer, 1000, 0);
>             if (res <= 0)
>                 break;
>         }
>         closesocket(MyProcPort->sock);
> And it works too.

I'm afraid this cure is probably worse than the disease, because
now the backend's exiting is held hostage by whether the client
closes its socket (and the resulting FIN reaches us, which it
might not if there's a network problem).

It might be safe to do the shutdown() only, since Microsoft
specifies that that doesn't block, but I have no idea if that
would improve matters.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16685: The ecpg thread/descriptor test fails sometimes on Windows
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #16685: The ecpg thread/descriptor test fails sometimes on Windows