Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martin Pitt <martin(at)piware(dot)de>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]
Date: 2006-03-26 16:33:47
Message-ID: 26643.1143390827@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Martin Pitt <martin(at)piware(dot)de> writes:
> The bug trail in [1] contains a followup from Tom that ignoring
> SIGPIPE is specifically intended. Is there any document which states
> the reason for that?

Allowing SIGPIPE to kill the backend is completely infeasible, as the
backend would be unable to release locks etc before dying.

We have occasionally talked about faking a QueryCancel if we notice
a write failure while sending to the client. Can't remember at the
moment what the outcome of those discussions was (ie, was there a
good reason not to) --- check the archives.

One point is that doing so doesn't help for queries that aren't
generating a lot of output, eg, updates/deletes.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-03-26 16:39:01 Re: Fwd: Bug#358546: failure of pg_ctl start -w -D
Previous Message Martin Pitt 2006-03-26 12:50:37 Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]