Tom Lane wrote:

>A bigger objection is that we couldn't get libssl to use it (AFAIK).
>The flag really needs to be settable on the socket (eg, via fcntl),
>not per-send.
>
It's a per-send flag, it's not possible to force it on with a fcntl :-(

What about an option to skip the sigaction calls for apps that can 
handle SIGPIPE? I'm not sure if an option at connect time, or a flag 
accessible through a function like PQsetnonblocking() is the better 
approach.

Attached is a patch that adds a connstr option, but I don't like it.

--
    Manfred

In response to

• Avoiding SIGPIPE (was Re: OSDL DBT-2 w/ PostgreSQL 7.3.4 and 7.4beta5) at 2003-11-01 19:20:46 from Tom Lane

Responses

• Re: Avoiding SIGPIPE (was Re: OSDL DBT-2 w/ PostgreSQL 7.3.4 and 7.4beta5) at 2003-11-01 21:37:25 from Tom Lane

pgsql-hackers by date

Next:	From: Manfred Spraul	Date: 2003-11-01 21:29:34
	Subject: Re: OSDL DBT-2 w/ PostgreSQL 7.3.4 and 7.4beta5
Previous:	From: Michael Mauger	Date: 2003-11-01 20:52:44
	Subject: Re: Proposal: psql force prompting on notty