[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 mcayland):

 Oh I'm not doubting that the problem exists, but my personal take is this:

 1) The problem has existed as long as PostGIS has used GEOS. The mailing
 list isn't flooded with hundreds of emails complaining about being unable
 to interrupt queries so it's hardly a pressing problem that needs to be
 solved right now. I'd much rather have a shorter 2.1 cycle (3-4 months)
 and put out something that's been through rigorous beta testing to squeeze
 out any potential memory corruption bugs.

 jatorre: in order to implement this, strk has had to add code to core
 parts of both PostGIS and GEOS. It's not just correcting a logic bug or
 similar, it really is a new feature. New code generally means new bugs.

 2) In your own words from comment 11: "Requires GEOS-3.4.0, and lots of
 testing...". The only way to test it properly will be to get people using
 it for real, and 2.0 branch is a stable branch, not the place for testing
 new code.

 3) The PSC agreed that point releases would be only be bugfix releases
 (mainly at the request of the PostgreSQL developers who were having
 problems with tracking bugs and API changes within point releases)

 4) This is contrary to your own position earlier within PostGIS
 development. At your request, I did not commit my initial implementation
 of the PROJ.4 cache to the latest 1.0 point release but to the 1.1 branch
 (see http://postgis.refractions.net/pipermail/postgis-
 devel/2005-November/001645.html), as you were concerned it would affect
 the stability of the 1.0 series despite the fact it was a live issue for
 us and we had been running the patches on live servers for several weeks.
 To make yourself an exception to the same rule is unfair upon all the
 other developers.

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