Re: libpq and psql not on same page about SIGPIPE

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, manfred(at)colorfullife(dot)com
Subject: Re: libpq and psql not on same page about SIGPIPE
Date: 2004-12-01 22:31:59
Message-ID: 41AE465F.7060605@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:

> If the C library does support queued signals then we will read the
> existing SIGPIPE condition and leave our own signal in the queue. This
> is no problem to the extent that one pending SIGPIPE looks just like
> another --- does anyone know of platforms where there is additional info
> carried by a SIGPIPE event?

POSIX.1b / SA_SIGINFO? SIGPIPE does not fill much of siginfo_t, but the
3rd handler arg has the interrupted execution context.

-O

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Manfred Spraul 2004-12-01 22:35:20 Re: libpq and psql not on same page about SIGPIPE
Previous Message Bruce Momjian 2004-12-01 22:30:57 Re: New compile warnings for inheritance

Browse pgsql-patches by date

  From Date Subject
Next Message Manfred Spraul 2004-12-01 22:35:20 Re: libpq and psql not on same page about SIGPIPE
Previous Message Tom Lane 2004-12-01 22:23:34 Re: [HACKERS] plperl Safe restrictions