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

Comment(by strk):

 So it turns out windows builds don't get the SIGINT delivered immediately,
 defeating the purpose of the handler. Indeed the PostgreSQL
 CHECK_FOR_INTERRUPTS call is more complex for windows, in that it
 explicitly flushes all non-ignored pending signals as well.

 We could replicate the complexity within the GEOS equivalent of the
 CHECK_FOR_INTERRUPTS function, or allow GEOS clients to pass a callback to
 invoke right before interrupt request checking to allow clients to do any
 flushing they might need.

 The second is likely to be more expensive as it'd mean a function call per
 check, rather than a simple variable lookup. Even worst it'd be a cross-
 library function call. Nothing dramatic, and only affecting windows, but
 worth mentioning.

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