[postgis-tickets] [PostGIS] #2976: geometry_columns performance on large databases

[PostGIS]

#2976: geometry_columns performance on large databases
-----------------------------------------+----------------------------------
 Reporter:  rnewton                      |       Owner:  pramsey      
     Type:  enhancement                  |      Status:  new          
 Priority:  medium                       |   Milestone:  PostGIS 2.2.0
Component:  postgis                      |     Version:  2.1.x        
 Keywords:  pgsql2shp, geometry_columns  |  
-----------------------------------------+----------------------------------
Changes (by robe):

  * milestone:  PostGIS 2.1.5 => PostGIS 2.2.0


Comment:

 rnewton,

 I've considered that and mentioned such a hack here.

 http://www.postgresonline.com/journal/archives/314-Materialized-
 geometry_columns-using-Event-Triggers.html


 I'm hesistant build that right into PostGIS because in 9.3 rebuilding a
 materialized view causes a read lock on the view so would just replace one
 set of problems for another.  In 9.4 that is much more of a possiblity to
 consider since it doesn't lock if we add a unique index on the view (which
 is easy to do), but since that doesn't work for prior versions and we have
 to support prior versions in 2.2, I'm afraid its still too much keep track
 of versions to make the benefit not more work to maintain than the gain.

 The idea of augmenting pgsql2shp to allow to explicitly specifying the
 projection might be worthwhile though and something we can look at in
 2.2.0

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