On Tue, Feb 19, 2013 at 4:38 AM, Pavel Stehule <pavel.stehule@xxxxxxxxx> wrote: > 2013/2/19 patrick keshishian <pkeshish@xxxxxxxxx>: >> On Tuesday, February 19, 2013, Albe Laurenz wrote: >>> >>> >>> One crude method would be to set statement_timeout to a nonzero >>> value - then queries that take longer than that many seconds >>> will be canceled. >> >> >> you don't truly mean to advise that, do you? :) > > it is not bad advice - usually all long queries should be cancelled by > timeout - and timeout is the most simple and sometimes good enough > solution. You can set timeout just for account used for login from web > application It would be nice if a long running query could occasionally check to see if it still has somewhere to send the results it is computing. Rather than running for hours only to give a "could not send data to client: Broken pipe" as soon as the first row becomes available. client_alive_timeout? Cheers, Jeff -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
