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

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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)tr>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Receiving SIGPIPE for PQfinish(<broken-connection>)
Date: 2006-04-23 04:09:58
Message-ID: 200604230409.k3N49wS25903@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
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. +

In response to

Responses

pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2006-04-24 04:02:11
Subject: Re: Building psql.exe using the free Borland compiler
Previous:From: Magnus HaganderDate: 2006-04-21 13:30:06
Subject: Re: libpq only WinXP?

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