Re: Avoiding SIGPIPE (was Re: OSDL DBT-2 w/ PostgreSQL - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Avoiding SIGPIPE (was Re: OSDL DBT-2 w/ PostgreSQL
Date
Msg-id 15119.1067793390@sss.pgh.pa.us
Whole thread Raw
In response to Re: Avoiding SIGPIPE (was Re: OSDL DBT-2 w/ PostgreSQL  (Manfred Spraul <manfred@colorfullife.com>)
Responses Re: Avoiding SIGPIPE (was Re: OSDL DBT-2 w/ PostgreSQL
List pgsql-hackers
Manfred Spraul <manfred@colorfullife.com> writes:
> Tom Lane wrote:
>> I don't see that this proposal adds any security.
>> 
> It's not about security:

The proposal would be more salable if it addressed the security problem
too.  As is, you are proposing putting a large wart on libpq's API in
order to work around an inefficiency that's only been shown to exist in
one version of one operating system.  I'd like to look for other
solutions before we do that.

One possibility that comes to mind is simply to test whether the SIGPIPE
handler is already SIG_IGN before we munge it.  Ideally we'd do that
once when the conn object is created, but even if it had to be done more
often, it might still be a net win.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: TODO item psql schema completion already implemented
Next
From: Tom Lane
Date:
Subject: Re: Experimental patch for inter-page delay in VACUUM