| From: | Florian Weimer <fw(at)deneb(dot)enyo(dot)de> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Douglas McNaught <doug(at)mcnaught(dot)org>, Zdenek Kotala <zdenek(dot)kotala(at)sun(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bug in signal handler |
| Date: | 2006-05-12 16:16:11 |
| Message-ID: | 87hd3v6wxg.fsf@mid.deneb.enyo.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Martijn van Oosterhout:
>> The fact remains that the postmaster has *always* been coded like that,
>> and we have *never* seen any problems. Barring proof that there is a
>> problem, I'm uninterested in rewriting it just because someone doesn't
>> like it.
>
> It should probably also be remembered that the "fix" would involve either
> polling the status by having select() return more often, or using
> sigsetjmp/siglongjmp. The cure is definitly worse than the disease.
The standard trick is to add a pipe to the select and write to that
from the signal handler. I'm not sure if it's worth the effort,
though.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-05-12 16:21:07 | Re: Clarification required |
| Previous Message | Tom Lane | 2006-05-12 15:06:42 | Re: any, anyelement, and anyarray |