[postgis-devel] [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.0.1
Component:  postgis  |     Version:  2.0.x        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by jatorre):

 Actually to me is a critical bug. Without PostGIS honoring PostgreSQL time
 outs, the database become quite sensitive. In some of our tests actually
 we could only take back PostgreSQL after a full restart when a nasty non
 interruptable function gets to spin. Somehow even PostgreSQL should even
 fire a warning alerting that a function is not behaving taken more time
 that what the system has give to him.

 So, I vote to have it as 2.0.1 and ensure that in future functions we can
 warranty that our functions are interruptable.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1802#comment:15>
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.