Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Dec 12, 2006 at 10:41:19PM -0500, Tom Lane wrote:
> "Brendan O'Shea" <brendanoshea@xxxxxxxxxxx> 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@xxxxxxxxx>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment: signature.asc
Description: Digital signature


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux