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

Re: Receiving SIGPIPE for PQfinish(<broken-connection>)

From: Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)tr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Receiving SIGPIPE for PQfinish(<broken-connection>)
Date: 2006-03-13 15:55:31
Message-ID: 20060313155531.GA191@alamut (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
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.)

Everything works fine when thread safety is enabled.


In response to


pgsql-interfaces by date

Next:From: Tom LaneDate: 2006-03-13 15:57:07
Subject: Re: Proposed p.tch for error locations
Previous:From: Tom LaneDate: 2006-03-13 15:44:24
Subject: Re: Proposed patch for error locations

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