Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: Statement timeout not working on broken connections with active queries
Date
Msg-id 266.1165981279@sss.pgh.pa.us
Whole thread Raw
In response to Statement timeout not working on broken connections with active queries  ("Brendan O'Shea" <brendanoshea@comcast.net>)
Responses Re: Statement timeout not working on broken connections with active queries  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
Tree view 
"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.

            regards, tom lane

pgsql-general by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: function accepting and returning rows; how to avoid parentheses
Next
From: Tom Lane
Date:
Subject: Re: resetting sequence to cur max value