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

From Peter Eisentraut
Subject Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]
Date
Msg-id 200603261948.54649.peter_e@gmx.net
Whole thread Raw
In response to Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]
List pgsql-bugs
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.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fwd: Bug#358546: failure of pg_ctl start -w -D
Next
From: "tao.shen"
Date:
Subject: BUG #2359: silent Installer for Postgresql 8.1.3 ignores BASEDIR