Utilize PAGC parser as drop in replacement for tiger normalizer
Now that we have the PAGC parser working with PostgreSQL 9.2 (have to test 9.1) and also working under my development environment - can now explore utilizing PAGC address normalizer as a drop in replacement for in-built tiger normalizer.
The plan is this:
Check if address_standardizer extension is installed, which is installable with command:
CREATE EXTENSION address_standardizer;
If it is installed, use it instead of packaged tiger geocoder normalize_address function to normalize the addresses.
I'm planning to have this packaged in winnie interim windows builds.
1) it seems I have to package along pcre*.dlls would be nice if I could just statically compile this into the address_standardizer.dll. I hate having all these extra children tagging along.
2) I'm tempted to say we should just include the rules.sql, lexicon.sql, gazeteer.sql as part of the extension. Perhaps having another field to denote which records are packaged so that users can customize and ensure their custom records are backed up.
I just think having to install 3 extra files ruins the beauty of extension.