[citruspi]

> It would be great if we stop adding features now... I wish there was a Postgres branch that took previous version and then just applied optimizations and bugfixes. No more.

To be fair, quoting from the article:

> There are no big new features in Postgres 13, but there are a lot of small but important incremental improvements. Let's take a look.

But also, in general, yes there are pieces of software that do this - most recently Moment.js[1]. There was some discussion earlier this week[2].

[1] https://momentjs.com/docs/#/-project-status/

[2] https://news.ycombinator.com/item?id=24477941

[chrisweekly]

It's unfortunate that performance is so rarely considered to be a feature.

[anarazel]

There's plenty performance work going on in postgres. Most major releases had significant improvements in some aspect of that.

[marcosdumay]

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.

[petergeoghegan]

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.

[koolba]

“.0” versions are the only versions that would have a major performance change. Anything else would be a fix version.