Slow queries on codespace attributes about 3dcitydb HOT 1 CLOSED

Well, you're free to create an index on all columns you want to filter on :)

I think, it's better to leave this up to the user. Every index requires disk space and - more important - affects write performance. So, we ship the 3DCityDB only with indexes on foreign key columns and spatial attributes (ok, and gmlid columns), which is a general recommendation for databases. One could argue that even some spatial indexes are not really necessary like the ones for terrain_intersection_curves.

In general, every database user should do some monitoring on his/her own to detect slow queries and create indexes.

from 3dcitydb.