Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Sun, 23 Apr 2006 00:09:58 -0400 (EDT)
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. +
- Follow-Ups:
- Re: Receiving SIGPIPE for PQfinish(<broken-connection>)
- From: Volkan YAZICI
- Re: Receiving SIGPIPE for PQfinish(<broken-connection>)
- Prev by Date: Re: libpq only WinXP?
- Next by Date: Re: Building psql.exe using the free Borland compiler
- Previous by thread: libpq only WinXP?
- Next by thread: Re: Receiving SIGPIPE for PQfinish(<broken-connection>)
- Indexes: