| From: | Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> |
|---|---|
| To: | 'Magnus Hagander ' <mha(at)sollentuna(dot)net>, 'Kurt Roeckx ' <Q(at)ping(dot)be> |
| Cc: | 'Tom Lane ' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, "'pgsql-hackers(at)postgresql(dot)org '" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: socket calls in signal handler (WAS: APC + socket r |
| Date: | 2004-03-09 00:38:39 |
| Message-ID: | A02DEC4D1073D611BAE8525405FCCE2B55F363@harris.memetrics.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> If that is indeed the case, I withdraw all my comments and misdirected
> ideas, and say we go for a win32 specific workaround :-)
We just need to be very careful on what this work-around is though...
For instance, whilst the idea of an "APCcalled" flag will work just fine,
mechanically, I'm extremely hesitant to adopt it until we *know* for sure
that, by making a socket call inside the APC, we aren't somehow munging
another part of the socket state. [after all, we didn't anticipate the
current issue]
Unfortunately, afaics, the MSDN documentation is pretty slim on details in
this regard.
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>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Natoli | 2004-03-09 00:49:38 | Re: socket calls in signal handler (WAS: APC + socket r |
| Previous Message | Bruce Momjian | 2004-03-08 23:50:53 | Re: Out of space situation and WAL log pre-allocation (was |