Re: Statement timeout not working on broken connections with active queries - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: Statement timeout not working on broken connections with active queries
Date
Msg-id 20061213125208.GA15546@svana.org
Whole thread Raw
In response to Re: Statement timeout not working on broken connections with active queries  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, Dec 12, 2006 at 10:41:19PM -0500, Tom Lane wrote:
> "Brendan O'Shea" <brendanoshea@comcast.net> writes:
> > Is there no way to specify a timeout for the write() to the socket or some
> > other way to abort?
>
> This is really a question to take up with your TCP stack implementors.
> I think it is fundamentally wrong for Postgres to be second-guessing
> the network software about whether a network connection is still live.

It would ofcourse be nice if postgres could honour signals while
writing to the client, but the currently that's hard to do.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment

pgsql-general by date:

Previous
From: Florian Weimer
Date:
Subject: Re: (Perl) script to set up an instance for regression tests
Next
From: Berend Tober
Date:
Subject: Re: resetting sequence to cur max value