Skip site navigation (1) Skip section navigation (2)

Re: Patch for select and APC on win32

From: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
To: 'Magnus Hagander' <mha(at)sollentuna(dot)net>,Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>,pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch for select and APC on win32
Date: 2004-03-23 22:35:15
Message-ID: A02DEC4D1073D611BAE8525405FCCE2B55F3AE@harris.memetrics.local (view raw or whole thread)
Lists: pgsql-patches
> >What I am wondering about now, is where else we need to change? AFAICS,
> >there is (at least?) one signal handler that performs sockets 
> >ops, namely Async_NotifyHandler.
> Actually, I don't think we need to do anything about that one. This
> signal handler is used in the backend (not postmaster), and the backend
> never calls selcet(). The other calls (recv, send etc) return correct
> return values even when a socket call is made in the APC, I'm fairly
> certain.

Not so sure. The reason I brought this up was because I tried the same test
(as I wrote before using select()) with recv(), and it returns -1 when
interrupted by an APC, which is ok, but errno is 0, and WSA/GetLastError
returns 997 (ERROR_IO_PENDING). [EINTR or WSAEINTR would have been nice].
Presumably send() also misbehaves.

Seems like it might actually be something to consider.


Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see 

pgsql-patches by date

Next:From: Christopher Kings-LynneDate: 2004-03-24 01:36:16
Subject: Re: dollar quoting and pg_dump
Previous:From: Andrew DunstanDate: 2004-03-23 22:15:00
Subject: Re: dollar quoting and pg_dump

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group