From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Volkan YAZICI <yazicivo@ttnet.net.tr>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Receiving SIGPIPE for PQfinish(<broken-connection>)
Date: Sun, 23 Apr 2006 00:09:58 -0400 (EDT)
Message-ID: <200604230409.k3N49wS25903@candle.pha.pa.us> (raw)
In-Reply-To: <20060313155531.GA191@alamut>
Did you ever get this fixed?
---------------------------------------------------------------------------
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.)
>
> Everything works fine when thread safety is enabled.
>
>
> Regards.
[ Attachment, skipping... ]
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: pgman@candle.pha.pa.us, yazicivo@ttnet.net.tr, tgl@sss.pgh.pa.us
Subject: Re: Receiving SIGPIPE for PQfinish(<broken-connection>)
In-Reply-To: <200604230409.k3N49wS25903@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox