Hacker News Reader

Comment by dimmke | Hacker News Reader

[flagged]

PG 15 has an EOL of Nov 2027, so you should be ok to stick with it for a while. ;)

It can be. We still running PG11 and 13 in production. Not obligated to upgrade - especially when the software is rock solid.

PG 11 is end-of-life, right? So you won't be getting new security updates. What's worse, libraries will stop supporting it over time, so you'll find it difficult to stay up to date in other places in your stack.

If I was running PG 11 in production, I'd be looking to upgrade sooner rather than later. Being on older-but-stable versions is good risk management, being on end-of-life version is not.

> PG 11 is end-of-life, right? So you won't be getting new security updates.

Not quite yet https://www.postgresql.org/support/versioning/ - the final release will be November 9, 2023.

We roll onto new stuff. So soon-ish the 11 will be replaced with a 14 or 15. And then later the 13 will roll up to whatever is good, stable and tested in our environment. And our roll-up plan has never seen an old PG lose client library access. PG has never ever, in 20+ years been the thing that holds us back. I also think risk-management has many more (important) factors than EOL.

Edit: quick check shows we also have PG9 and PG10 in some Live roles too.

Whenever you do a one day full of updates and fix small issues but also gain new features and performance, just remember there is someone who uses some super old db no one wanna touch it again and the migration of that old thing will take weeks!

Reply on news.ycombinator.com