Re:Things we learned running Postgres 13
by chrisweekly on Monday September 21, 2020 @03:09PM
(#24547191)
It's unfortunate that performance is so rarely considered to be a feature.
[ Parent
| on HN ]
Re:Things we learned running Postgres 13
by anarazel on Monday September 21, 2020 @03:28PM
(#24547423)
There's plenty performance work going on in postgres. Most major releases had significant improvements in some aspect of that.
Re:Things we learned running Postgres 13
by marcosdumay on Monday September 21, 2020 @03:15PM
(#24547248)
Postgres usually adds plenty of performance from one version to another.
Not much on .0 versions, those are more feature packed, but all the other time.
Re:Things we learned running Postgres 13
by petergeoghegan on Monday September 21, 2020 @03:24PM
(#24547374)
Actually, Postgres does not add any performance features to point releases at all. Point releases are only for bug fixes. You may be thinking of MySQL.
Occasionally, there are cases that could be argued to be exceptions to the general rule. But that's a hard argument to make -- everything committed to a back branch is officially a bug fix. Things like optimizer regression fixes are "performance enhancements" in a certain sense, but are nevertheless justified as bug fixes.
Re:Things we learned running Postgres 13
by koolba on Monday September 21, 2020 @03:18PM
(#24547302)
“.0” versions are the only versions that would have a major performance change. Anything else would be a fix version.
[dead]
I've reopened your comment upthread for editing. Please don't post off topic complaints like this though. The guidelines ask you not to go on about downvotes and also not to use allcaps for emphasis.
https://news.ycombinator.com/newsguidelines.html
Edit: I've re-closed the comment but if you want to add to it, you're welcome to email [email protected].
The moment.js author just said that no more changes would be added, so that's one recent example. People were praising the decision in the HN thread.