| From: | Manfred Spraul <manfred(at)colorfullife(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | markw(at)osdl(dot)org, pgsql-hackers(at)postgresql(dot)org, osdldbt-general(at)lists(dot)sourceforge(dot)net |
| Subject: | Re: OSDL DBT-2 w/ PostgreSQL 7.3.4 and 7.4beta5 |
| Date: | 2003-11-01 19:10:42 |
| Message-ID: | 3FA40532.2050802@colorfullife.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>Manfred Spraul <manfred(at)colorfullife(dot)com> writes:
>
>
>>signal handlers are a process property, not a thread property - that
>>code is broken for multi-threaded apps.
>>
>>
>
>Yeah, that's been mentioned before, but I don't see any way around it.
>
Do not handle SIGPIPE on multithreaded apps, and ask the caller to do
that? The current code doesn't block SIGPIPE reliably, which makes it
totally useless (except that it's a debugging nightmare, because
triggering it depends on the right timing).
>What we really want is to turn off SIGPIPE delivery on our socket
>(only), but AFAIK there is no API to do that.
>
>
Linux has as MSG_NOSIGNAL flag for send(), but that seems to be Linux
specific.
--
Manfred
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-11-01 19:12:49 | Re: Experimental patch for inter-page delay in VACUUM |
| Previous Message | Tom Lane | 2003-11-01 18:37:30 | Re: OSDL DBT-2 w/ PostgreSQL 7.3.4 and 7.4beta5 |