Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 1 Apr 2004 18:25:40 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Postgres Backend doesn't catch the next command, after SIGUSR2 Message-ID: <20040401162540.GD2598@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040330094430 DOT GG17229 AT cygbert DOT vinschen DOT de> <20040401063610 DOT 19229 DOT qmail AT web60309 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040401063610.19229.qmail@web60309.mail.yahoo.com> User-Agent: Mutt/1.4.2i 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 AT cygwin DOT 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/