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

[PostGIS]

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

Comment(by mcayland):

 What was the resulting effect on performance by adding
 CHECK_FOR_INTERRUPTS to the allocators? Memory allocation is already known
 to be a PostgreSQL performance bottleneck, so it strikes me that this
 could have a significant effect on queries with large datasets/long query
 times. Can you provide the before and after numbers for a test query on a
 reasonably-sized dataset (several million records)?

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