Re: Statement timeout not working on broken connections with active queries

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Brendan O'Shea" <brendanoshea(at)comcast(dot)net>
Cc: "Brian Wipf" <brian(at)clickspace(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Statement timeout not working on broken connections with active queries
Date: 2006-12-13 03:41:19
Message-ID: 266.1165981279@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Brendan O'Shea" <brendanoshea(at)comcast(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-12-13 03:48:10 Re: resetting sequence to cur max value
Previous Message Merlin Moncure 2006-12-13 03:19:38 Re: function accepting and returning rows; how to avoid parentheses