4 ms·
Postgres however has moved quite a way since 2016 when the post was written, so it is possibly even factually incorrect at 2018. Postgres switched to much more
by watt 8y ago
Postgres however has moved quite a way since 2016 when the post was written, so it is possibly even factually incorrect at 2018.
Postgres switched to much more rapid release scheme, and is making a lot of ergonomic and performance improvements since they got the "correctness" part down (such as auto vacuum, etc), which only came together in last couple years.
- Operyl 8y agoI feel like the 2016 tag is extremely useful in letting users figure this out, though. And the new discourse that flows from this (read some of the other comments in here, they're explaining that Postgres took a hard look at themselves and adapted).