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

 Okay the good news is the most trivial of functions I can come up with is
 wrappable (dissolves into the main plan), but doesn't seem to allow higher
 than this:


 {{{
 CREATE OR REPLACE FUNCTION pagc_standardize(micro text,macro text) RETURNS
 stdaddr AS
   $$
    SELECT standardize_address('pagc_lex'
        , 'pagc_gaz'
        , 'pagc_rules'
        , $1, $2 ) AS std  ;
 $$
 language 'sql';
 }}}
 The bad news it has to be like that.  As soon as I try to return as an OUT
 param or try to throw the parse address in there, PostgreSQL refuses to
 fold into the main plan and I loose the caching.

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