[postgis-tickets] [PostGIS] #3347: Loader functions rely on the order of columns be returned in ordinal_position order (was: county_all, county_all_lookup not loading for Tiger 2015)

[PostGIS]

#3347: Loader functions rely on the order of columns be returned in
ordinal_position order
-----------------------------+---------------------------
  Reporter:  robe            |      Owner:  robe
      Type:  defect          |     Status:  reopened
  Priority:  blocker         |  Milestone:  PostGIS 2.2.1
 Component:  tiger geocoder  |    Version:  trunk
Resolution:                  |   Keywords:
-----------------------------+---------------------------
Changes (by robe):

 * status:  closed => reopened
 * resolution:  invalid =>


Comment:

 Okay there is an issue here.  I'm not sure why I never ran into it before.
 It could be because this particular database has more than a thousand
 tables so the query planner does something different.

 The fundamental issue is that when building list on columns, the loader is
 assuming the columns in information_schema.columns will be returned in
 ordinal position if no order by is specified.  This is not the case with
 this particular database anyway.

 I think someone actually complained about this but I didn't understand why
 they tried to change the load scripts and why it was failing on their
 system.  Anyway it's a simple fix.

 Will test and upport and backport after I have tested my patch.

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