4 ms·
It is very well supported and also loved by the community as far as I see, also I’ve been a long MySQL user so PostgreSQL should be a fairly familiar tool. The
by mattrighetti 5y ago
It is very well supported and also loved by the community as far as I see, also I’ve been a long MySQL user so PostgreSQL should be a fairly familiar tool. The easier thing with OpenStreetMap maybe is that it can cache a lot of stuff to serve it faster since most of the features is contains remain “static” and unchanged, I can’t always do this since I have to add and remove stuff very very often and still get a response back as fast as possible to not annoy users. I guess I’ll have to try it out and see what works out best
- 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.