Skip site navigation (1) Skip section navigation (2)

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 22:52:31
Message-ID: 200401302252.i0UMqV124041@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Scott Lamb wrote:
> You could just do a pthread_sigmask() before and after the 
> pthread_setspecific() to guarantee that no SIGPIPE will arrive on that 
> thread in that time. I think it's pretty safe to assume that as long as 
> you're not doing a pthread_[gs]etspecific() on that same pthread_key_t, 
> it's safe.


I call pthread_setspecific() in the SIGPIPE handler.  How sdoes
pthread_sigmask() help me at that point?

-- 
  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

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2004-01-30 22:53:55
Subject: Re: Mixing threaded and non-threaded
Previous:From: Hannu KrosingDate: 2004-01-30 22:48:03
Subject: Re: returning PGresult as xml

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group