id summary reporter owner description type status priority milestone component version resolution keywords cc 2365 find_srid performance regression with large numbers of tables angrygoat pramsey "The speed of find_srid has dropped significantly in PostGIS >= 2.0 when a large number of tables exist in the database. It looks like this is related to the new definition of geometry_columns as a view. On my system, for a database containing a hundred tables find_srid() takes ~ 10ms, with five thousand tables ~ 100ms, with fifteen thousand tables ~ 450ms. I'm not sure if this is a bug or a regression you'd consider worth fixing, however mapserver's postgis vector data source will put a find_srid() call in every query if the user doesn't specify ""using srid="". With PostGIS>=2.0 on a database with lots of tables, not specifying the srid is suddenly a massive (rather than very minor) performance issue. I've attached a rather ugly shell script that reproduces the issue :-) Thanks!" defect closed medium PostGIS 2.1.8 postgis 2.0.x fixed history keithmoss