Re: Postgres Backend doesn't catch the next command, after SIGUSR2

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Mar 31 22:36, Patrick Samson wrote:
> > > if (!CancelIo ((HANDLE) socket))
> > >   {...}
> > > else
> > >   {
> > >    if (WSAGetOverlappedResult (socket, &ovr, &len,
> > >  FALSE, flags) && len != 0)
> > >     ret = (int) len;
> > >    else WSASetLastError (WSAEINTR);
> > 
> > Did you try it?
> 
> Yes. It worked.
> I ran my test case this night for 30000 runs.
> 
> > Yesterday I changed Cygwin to use
> > asynchronous I/O
> > instead of overlapped I/O so it now can do without
> > CancelIo.
> > However, two people reported hangs which don't occur
> > for me.  If
> > if takes too long to track down, I guess I'll revert
> > to overlapped
> > I/O plus your patch.  But I would be more happy with
> > a working
> > async I/O solution.
> 
> Is it still worth?

We're still experimenting with async I/O but there's perhaps a point
where reverting to overlapped makes sense.  I'm glad to have your
patch for that case.

Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/