3 ms·
> since I have to add and remove stuff Ok... Then how do you have "read-intensive geospatial queries?". The phrase "read-intensive" implies far more reads th
by pwg 5y ago
> since I have to add and remove stuff
Ok... Then how do you have "read-intensive geospatial queries?".
The phrase "read-intensive" implies far more reads than writes, yet your response above implies you will be doing a lot of writes.
- mattrighetti 5y agoReads are going to be way larger than insert/delete/update.
- pwg 5y agoWhich would mean "most of the features is contains remain “static” and unchanged" and being able to cache will be just as valuable to you as it is to OpenStreetMap. And, for the record, OpenStreetMap is not static. An enormous number of changes arrive to OSM daily from mappers all over the world making changes to keep the map up to date. https://munin.openstreetmap.org/openstreetmap.org/albi.openstreetmap.org/index.html#postgresql https://munin.openstreetmap.org/openstreetmap.org/albi.opens... And Postgresql is behind all of it.