Re: [RFC,PATCH] SIGPIPE masking in local socket connections

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeremy Kerr <jk(at)ozlabs(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [RFC,PATCH] SIGPIPE masking in local socket connections
Date: 2009-06-02 14:11:11
Message-ID: 11313.1243951871@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeremy Kerr <jk(at)ozlabs(dot)org> writes:
>> The consideration is that the application fails completely on server
>> disconnect (because it gets SIGPIPE'd). This was long ago deemed
>> unacceptable, and we aren't likely to change our opinion on that.

> OK, understood. I'm guessing MSG_NOSIGNAL on the send() isn't portable
> enough here?

Well, it's certainly not 100% portable, but I wouldn't object to a patch
that tests for it and uses it where it works.

One question that might be a bit hard to answer is whether mere
existence of the #define is sufficient evidence that the feature works.
We've had problems before with userland headers not being in sync
with what the kernel knows.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2009-06-02 14:16:05 Re: [RFC,PATCH] SIGPIPE masking in local socket connections
Previous Message Bruce Momjian 2009-06-02 14:07:11 Re: pg_migrator and making columns invisible