Date: Mon, 24 Apr 2006 13:17:05 +0300
From: Volkan YAZICI <yazicivo@ttnet.net.tr>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-interfaces@postgresql.org
Subject: Re: Receiving SIGPIPE for PQfinish(<broken-connection>)
Message-ID: <20060424101705.GB259@alamut>
References: <20060313155531.GA191@alamut>
	<200604230409.k3N49wS25903@candle.pha.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200604230409.k3N49wS25903@candle.pha.pa.us>
User-Agent: Mutt/1.4.2.1i

On Apr 23 12:09, Bruce Momjian wrote:
> Did you ever get this fixed?

Actually, I couldn't reproduce same error on my current system -
although, as I understand, none of the related source files were
modified. (That failure was reported using Debian Sarge 3.1, so
it could be caused by buggy debian libraries - like their buggy
getpw..._r() family.)

> Volkan YAZICI wrote:
> > On Mar 12 11:18, Tom Lane wrote:
> > > pqsecure_write should have disabled SIGPIPE already.  You should look
> > > into why that is seemingly not working.
> > 
> > When I omit --enable-thread-safety, code doesn't handle in the case of
> > a SIG_ERR return on the call to pqsignal() made from pqsecure_write().
> > 
> > Furthermore, I still couldn't figure out why pqsignal() cannot handle
> > SIGPIPE - despite pqsignal() doesn't return SIG_ERR. (A related small
> > debug output is attached.)

I don't have much experience with signal handling but if any hacker will
ever get chance to take a look at SIG_ERR returning pqsignal() calls'
handling, above problem (?) will be clarified.

> > Everything works fine when thread safety is enabled.

What are the reasons for thread-safety is not enabled by default? Is
this because related system may not support thread locking to be used in
libpq?


Regards.