| From: | Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> |
|---|---|
| To: | 'Tom Lane ' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 'Bruce Momjian ' <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | 'Jan Wieck ' <JanWieck(at)Yahoo(dot)com>, Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, "'''pgsql-patches(at)postgresql(dot)org' ' '" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: fork/exec patch: pre-CreateProcess finalization |
| Date: | 2004-01-09 01:04:40 |
| Message-ID: | A02DEC4D1073D611BAE8525405FCCE2B55F238@harris.memetrics.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> BTW, how are we going to do cancels in Windows-land? The sub-postmaster
> isn't gonna have access to the postmaster's list of child PIDs and
> cancel keys ...
Good question (the Win32/EXEC_BACKEND case is #def'd out to issue an
altogether unhelpful abort(), so I know it is there).
The only things I've thought of so far are:
a) sticking the PID/cancel key list in shared mem [yeech]
b) rearranging the entire cancel handling to occur in the postmaster [double
yeech]
Any better ideas?
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>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Natoli | 2004-01-09 01:12:32 | Re: fork/exec patch: pre-CreateProcess finalization |
| Previous Message | Tom Lane | 2004-01-09 00:59:26 | Re: fork/exec patch: pre-CreateProcess finalization |