Re: Idea: quicker abort after loss of client connection

From: ncm(at)zembu(dot)com (Nathan Myers)
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Idea: quicker abort after loss of client connection
Date: 2001-06-06 19:43:22
Message-ID: 20010606124322.Q18121@store.zembu.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 05, 2001 at 08:01:02PM -0400, Tom Lane wrote:
>
> Thoughts? Is there anything about this that might be unsafe? Should
> QueryCancel be set after *any* failure of recv() or send(), or only
> if certain errno codes are detected (and if so, which ones)?

Stevens identifies some errno codes that are not significant;
in particular, EINTR, EAGAIN, and EWOULDBLOCK. Of these, maybe
only the first occurs on a blocking socket.

Nathan Myers
ncm(at)zembu(dot)com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2001-06-06 19:43:53 And what about that Debugfile?
Previous Message The Hermit Hacker 2001-06-06 19:08:15 Re: Dual-CPU slower then Single under HP?