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

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: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org, Martin Pitt <martin(at)piware(dot)de>
Subject: Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]
Date: 2006-03-27 01:34:46
Message-ID: 29170.1143423286@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane wrote:
>> Allowing SIGPIPE to kill the backend is completely infeasible, as the
>> backend would be unable to release locks etc before dying.

> So the upshot is really not that ignoring SIGPIPE is specifically 
> intended as the optimal solution but that writing a proper cleanup 
> handler for SIGPIPE seems very difficult.

Well, if we did want to change this it would be far easier and safer to
do the other thing (ie, set QueryCancel upon noticing a write failure).

The question is whether doing either one is really a material
improvement, seeing that neither is going to provoke an abort
until/unless the backend actually tries to write something to the client.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: JP GluttingDate: 2006-03-27 10:20:23
Subject: BUG #2360: Backup produces "ERROR: could not convert UTF8 character to ISO8859-1"
Previous:From: tao.shenDate: 2006-03-27 00:34:30
Subject: BUG #2359: silent Installer for Postgresql 8.1.3 ignores BASEDIR

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