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

What's left?

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org>
Cc: "Claudio Natoli" <claudio(dot)natoli(at)memetrics(dot)com>,"PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: What's left?
Date: 2004-01-22 14:59:51
Message-ID: 303E00EBDD07B943924382E153890E5434AA6C@cuthbert.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
Hello,

I think it's safe to say there is a working implementation of a signal
handler.  The one tricky part left is to identify some smart places for
the backend to check the awaiting signal queue.  The first one is easy:
switch recv() with select() with a reasonable timeout and a poll.

If and when the signal handler gets patched into CVS, is there anything
else left that prevents the cvs version from compiling and linking?
From what I understand, Claudio's fork/exec implementation is either
complete or nearly complete.  

I would like very much to help any way possible in solving any last
remaining issues.  Once the CVS sources are compliable, it will be
easier to make meaningful contributions.  I'm really looking forward to
testing and benchmarking the win32 port.  A big thanks to all who
continue to work so hard on this project.

Merlin



pgsql-hackers by date

Next:From: Jean-Michel POUREDate: 2004-01-22 15:15:36
Subject: PostgreSQL installation CD based on Morphix
Previous:From: Jan WieckDate: 2004-01-22 14:20:58
Subject: Re: cache control?

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2004-01-22 15:53:33
Subject: Re: Singnals code (not just win32 specific)
Previous:From: Jan WieckDate: 2004-01-22 13:34:35
Subject: Re: Singnals code (not just win32 specific)

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