[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:  reopened     
  Priority:  medium               |   Milestone:  PostGIS 2.1.0
 Component:  pagc_address_parser  |     Version:  trunk        
Resolution:                       |    Keywords:               
----------------------------------+-----------------------------------------

Comment(by robe):

 Getting warmer.  For first phase this should do fine, but still can't do
 as a drop in replace for the main function without losing speed
 unfortunately so it still requires different calling for users to achieve
 same speed because as soon as I try to incorporate it in a plpgsql
 function, I lose the cache and while I can hide some of the plumbing in
 SQL functions and CASTS, an SQL function has both the beauty and ugliness
 of being transparent.  The transparency hurts during install because
 postgres tries to validate it and will fail if address_standardizer is not
 installed  So to hide it in SQL functions I have to require the pagc to be
 installed or wrap it in a bridge extension.  None of which is all that
 appealing.

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