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

PostGIS trac at osgeo.org
Wed Jun 6 09:06:40 PDT 2012


#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 strk):

 The attached interrupt.sql script may be used for testing purposes.
 Run with: $ time psql -f interrupt.sql
 It is expected that the query ends with something like:
 {{{
 ERROR:  GEOSBuffer: InterruptedException: Interrupted!
 }}}

 and it takes no much longer than 1 second to finish.

 I tested with with PostgreSQL 8.4.10 and 9.1.2, GEOS-3.4.0dev r3663,
 postgis 2.1.0svn r9851 and postgis 2.0.1svn r9849 with the macro defined.

 postgis 2.0.1svn r9849 without the macro defined completes (interrupting)
 in about 43 seconds instead.

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


More information about the postgis-devel mailing list