[postgis-tickets] [PostGIS] #1802: Ensure interruptability of long-running calls

[PostGIS]

#1802: Ensure interruptability of long-running calls
---------------------+------------------------------------------------------
 Reporter:  strk     |       Owner:  strk         
     Type:  task     |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.1.0
Component:  postgis  |     Version:  2.0.x        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by strk):

 I belive this is open as it's missing testcases.
 A testcase could do something like setting a very short statement timeout
 and invoking a very expensive GEOS query. It'd be a pretty fuzzy test in
 that it's success would depend by the timeout being long enough not to
 kick before GEOS starts and short enough not to kick after GEOS ends, and
 it will be also dependent on GEOS, and on the machine. Tricky one.

 Maybe the test should be independent from the others and first run the
 expensive query once to time it, then set timeout to half of that and run
 again, taking in consideration also cold vs. warm runs...

 Did anyone get excited enough to work on it ? :)

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1802#comment:31>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.