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

From Tom Lane
Subject Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]
Date
Msg-id 14128.1143471038@sss.pgh.pa.us
Whole thread Raw
In response to Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]
List pgsql-bugs
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> On Sun, Mar 26, 2006 at 08:34:46PM -0500, Tom Lane wrote:
>> The question is whether doing either one is really a material
>> improvement, seeing that neither is going to provoke an abort
>> until/unless the backend actually tries to write something to the client.

> Is there a server equivalent to PQstatus? If there were one, couldn't
> the server periodically ping the client?

No, and do you really want the server stopping its processing of the
query just to go see if the client is still alive?  This would slow
things down and introduce a whole new failure mode, ie, client doesn't
answer ping fast enough so its session gets aborted.

(Just for the record, PQstatus isn't a "ping" operation either.)

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Tomasz Ostrowski"
Date:
Subject: BUG #2362: bug reporting form: "submit" shows only "&id=[number]"
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Followup comment for bug report 'postmaster ignores SIGPIPE' [was: Bug#255208: Would help with client aborts, too.]