| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Brendan O'Shea <brendanoshea(at)comcast(dot)net>, 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 12:52:08 |
| Message-ID: | 20061213125208.GA15546@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Dec 12, 2006 at 10:41:19PM -0500, Tom Lane wrote:
> "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.
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(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Berend Tober | 2006-12-13 13:27:48 | Re: resetting sequence to cur max value |
| Previous Message | Florian Weimer | 2006-12-13 11:22:47 | Re: (Perl) script to set up an instance for regression tests |