

> IMO, it's time for a second run of the code, and a functional test which
> simulates the command processing loop which should include:
> 
> 1. setjmp/longjmp stack manipulation (i.e. ELOG)
> 2. in process/out of process generates signals
> 3. all thread mechanisms.

Definitely. Magnus, I assume you have an interest in continuing this? (if
not,  I'll gladly take it over, but I suspect you'll be wanting to ;-)

In any case, I'll independently see if I can get this mechanism wedged into
my win32 code base, and actually try it within postgres itself (when I get
the chance).

Cheers,
Claudio
--- 
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see 
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>

Wed, 14 Jan 2004 10:43:18 +1100
Claudio Natoli <claudio.natoli@memetrics.com>
Re: [pgsql-hackers-win32] Win32 signal code - first try