Shaun Thomas <sthomas@townnews.com> writes:
>> Note you could implement such a time limit purely on the client side,
>> which might be an easier and more flexible way to go.
> That's just it. PHP (our front end) has a 30 second time limit we
> have not overridden. But we've found that after the PHP execution stops
> in disgust, the postgres thread keeps going until we restart the
> postgres back end.
Sounds like PHP is not actually trying to cancel the query when it
gives up waiting. Anyone care to go in and fix that?
regards, tom lane