Re: Mixing threaded and non-threaded

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Scott Lamb <slamb(at)slamb(dot)org>
Cc: Manfred Spraul <manfred(at)colorfullife(dot)com>, Steve Atkins <steve(at)blighty(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Mixing threaded and non-threaded
Date: 2004-01-30 17:25:05
Message-ID: 200401301725.i0UHP5i12779@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Scott Lamb wrote:
> Speaking of async signal-safe functions, pthread_getspecific() isn't
> specified to be (and thus PQinSend() and thus
> sigpipe_handler_ignore_send()). It's probably okay, but libpq is
> technically using undefined behavior according to SUSv3.

Yikes. I never suspected pthread_getspecific() would not be signal safe
because it is already thread safe, but I see the point that it is called
in the current thread. Any ideas how to fix this?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message BARTKO, Zoltan 2004-01-30 17:33:09 Re: msg translation into sk_SK, Docs: SGML -> XML
Previous Message Bruce Momjian 2004-01-30 17:21:54 Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint