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

Re: Avoiding SIGPIPE (was Re: OSDL DBT-2 w/ PostgreSQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Manfred Spraul <manfred(at)colorfullife(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Avoiding SIGPIPE (was Re: OSDL DBT-2 w/ PostgreSQL
Date: 2003-11-02 17:16:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Manfred Spraul <manfred(at)colorfullife(dot)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

In response to


pgsql-hackers by date

Next:From: Jon PastoreDate: 2003-11-02 17:44:20
Subject: suggestion for error statements
Previous:From: Peter EisentrautDate: 2003-11-02 17:16:04
Subject: Re: TODO item psql schema completion already implemented

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