3 ms·

The arguments here aren't great. It's also mentioned to install some other extension (why, then, not use PostGIS at this point?). Don't really understand what t

The arguments here aren't great. It's also mentioned to install some other extension (why, then, not use PostGIS at this point?). Don't really understand what the author was getting at. Also, as was mentioned, this was posted earlier today: https://news.ycombinator.com/item?id=22820485 https://news.ycombinator.com/item?id=22820485

derefr 7y ago
The "other extensions" are part of Postgres core, and are just "extensions" in the sense that they're loadable modules that are not loaded by default. PostGIS is a whole big external thing that Postgres doesn't ship with. Any running Postgres cluster can load and use the extensions in the article, with no ops work. Even environments like RDS have these extensions available. If you want PostGIS, you need to explicitly run PostGIS; if you want PostGIS-as-a-Service, you need to find someone who is explicitly offering PostGIS-as-a-Service.
- beering 7y ago
  Worth pointing out that RDS includes PostGIS, which is good since you can't poke the DB server directly. Although I am sympathetic to the blog post, since PostGIS is overkill in complexity for simple use cases like a store locator.
  - redis_mlc 7y ago
    Redis has GIS features built-in for store locator type calculations, so that's another option: https://redislabs.com/redis-best-practices/indexing-patterns/geospatial/ https://redislabs.com/redis-best-practices/indexing-patterns... Here's a couple Lyft talks: Redis at Lyft: 1,000 Instances (2017) https://www.youtube.com/watch?v=U4WspAKekqM https://www.youtube.com/watch?v=U4WspAKekqM Geospatial Indexing: The 10 Million QPS Redis Architecture Powering Lyft (2017) https://www.youtube.com/watch?v=cSFWlF96Sds https://www.youtube.com/watch?v=cSFWlF96Sds (2017)
ris 7y ago
I think it's still very valuable to raise awareness of the existence of a lot of these more basic features in postgres core. Though I think it would be better titled "You might not need PostGIS".

derefr 7y ago

The "other extensions" are part of Postgres core, and are just "extensions" in the sense that they're loadable modules that are not loaded by default. PostGIS is a whole big external thing that Postgres doesn't ship with. Any running Postgres cluster can load and use the extensions in the article, with no ops work. Even environments like RDS have these extensions available. If you want PostGIS, you need to explicitly run PostGIS; if you want PostGIS-as-a-Service, you need to find someone who is explicitly offering PostGIS-as-a-Service.

beering 7y ago
Worth pointing out that RDS includes PostGIS, which is good since you can't poke the DB server directly. Although I am sympathetic to the blog post, since PostGIS is overkill in complexity for simple use cases like a store locator.
- redis_mlc 7y ago
  Redis has GIS features built-in for store locator type calculations, so that's another option: https://redislabs.com/redis-best-practices/indexing-patterns/geospatial/ https://redislabs.com/redis-best-practices/indexing-patterns... Here's a couple Lyft talks: Redis at Lyft: 1,000 Instances (2017) https://www.youtube.com/watch?v=U4WspAKekqM https://www.youtube.com/watch?v=U4WspAKekqM Geospatial Indexing: The 10 Million QPS Redis Architecture Powering Lyft (2017) https://www.youtube.com/watch?v=cSFWlF96Sds https://www.youtube.com/watch?v=cSFWlF96Sds (2017)

ris 7y ago

I think it's still very valuable to raise awareness of the existence of a lot of these more basic features in postgres core. Though I think it would be better titled "You might not need PostGIS".