Re: Killing "stuck" queries and preventing queries from getting "stuck" - Mailing list pgsql-general

From Tom Lane
Subject Re: Killing "stuck" queries and preventing queries from getting "stuck"
Date
Msg-id 13583.1285641573@sss.pgh.pa.us
Whole thread Raw
In response to Killing "stuck" queries and preventing queries from getting "stuck"  (Tim Uckun <timuckun@gmail.com>)
Responses Re: Killing "stuck" queries and preventing queries from getting "stuck"  (Tim Uckun <timuckun@gmail.com>)
List pgsql-general
Tim Uckun <timuckun@gmail.com> writes:
> Is there a way to tell postgres to stop any query that runs longer
> than a specified amount of time? Say an hour?

Setting statement_timeout would do that.  You ought to figure out
what's causing the performance problem, though, instead of just
zapping things ...

            regards, tom lane

pgsql-general by date:

Previous
From: Tim Uckun
Date:
Subject: Re: Deleting orphaned records (not exists is very slow)
Next
From: Michael Glaesemann
Date:
Subject: Re: Deleting orphaned records (not exists is very slow)