Re: Idea: quicker abort after loss of client connection

Поиск
Список
Период
Сортировка
От ncm@zembu.com (Nathan Myers)
Тема Re: Idea: quicker abort after loss of client connection
Дата
Msg-id 20010606124322.Q18121@store.zembu.com
обсуждение исходный текст
Ответ на Idea: quicker abort after loss of client connection  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Idea: quicker abort after loss of client connection  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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@zembu.com


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: And what about that Debugfile?
Следующее
От: Thomas Lockhart
Дата:
Сообщение: Re: Timestamp change - 8601 compliance