[postgis-tickets] [PostGIS] #2260: Benchmarking speed between built-in tiger normalizer and pagc_address_parser

[PostGIS]

#2260: Benchmarking speed between built-in tiger normalizer and
pagc_address_parser
---------------------------------+------------------------------------------
 Reporter:  robe                 |       Owner:  robe         
     Type:  task                 |      Status:  new          
 Priority:  medium               |   Milestone:  PostGIS 2.1.0
Component:  pagc_address_parser  |     Version:  trunk        
 Keywords:                       |  
---------------------------------+------------------------------------------

Comment(by woodbri):

 Ok posted the problem on the pgsql-hackers list and Tom Lane replied with:

   You can't hold a SPI context open across multiple calls of an SRF.
   Even if it somehow failed to malfunction in isolation, this would
   certainly not work in a query where some other called function was
   also using SPI.

   Possibly the reason the code accidentally fails to malfunction on Linux
   is you're not using an --enable-cassert build there?  That would wipe
   freed memory and thus help to reveal errors of this sort consistently,
   whereas otherwise the failures would be context-dependent.

 So I guess I have to figure out how to save the contents of my
 SPI_tuptable into another context that can be held across SRF calls.

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