News for hackers. Stuff that matters.
Re:Why Does Everyone Run Ancient Postgres Versions? by justin_oaks on Thursday October 17, 2024 @08:36PM (#41875268)
My upgrade policy for everything:

Significant security vulnerability? Upgrade

Feature you need? Upgrade

All other reasons: Don't upgrade.

Upgrading takes effort and it is risky. The benefits must be worth the risks.

Re:Why Does Everyone Run Ancient Postgres Versions? by hinkley on Thursday October 17, 2024 @11:44PM (#41876163)
Once your version doesn’t receive security fixes you’re one CERT advisory away from having your whole week pre-empted by an emergency upgrade.

I’ve been there with products that were still internal at the time. I can only imagine how much fun that is with a public product. But then I do have a pretty vivid imagination. We changed to periodic upgrades after that to avoid the obvious problem staring us in the face.

Re:Why Does Everyone Run Ancient Postgres Versions? by Gigachad on Friday October 18, 2024 @12:06AM (#41876254)
Eventually you get forced to update it when the other stuff you use starts having minimum version requirements.
Re:Why Does Everyone Run Ancient Postgres Versions? by natmaka on Thursday October 17, 2024 @08:52PM (#41875370)
Suggestion: add "End of life (no more maintenance for this version)? Upgrade"
Re:Why Does Everyone Run Ancient Postgres Versions? by Gormo on Thursday October 17, 2024 @11:51PM (#41876193)
Why? If the implemented featureset meets your needs, and there are no unresolved bugs or security vulnerabilities relevant to your use cases, what further "maintenance" do you need?
Re:Why Does Everyone Run Ancient Postgres Versions? by abraham on Friday October 18, 2024 @12:04AM (#41876247)
When a critical security patch comes out, you don't want to have to to do a major version upgrade to get it.
Re:Why Does Everyone Run Ancient Postgres Versions? by FearNotDaniel on Friday October 18, 2024 @12:54AM (#41876460)
Because when the maintainers have stopped patching that version against all known security vulnerabilities, that doesn't stop the bad guys from looking for more vulnerabilities. When they find one, it will get exploited. So you either wake up to an email from Have I Been Pwned to say all your customer data has been exfiltrated [0], or (if you're lucky) you have a mad scramble to do that update before they get you.

[0] Probably including those passwords you didn't hash, and those credit card numbers you shouldn't be storing in the first place because, what the heck, it meets your needs.

Re:Why Does Everyone Run Ancient Postgres Versions? by throwaway918299 on Thursday October 17, 2024 @09:07PM (#41875465)
Here’s another reason to upgrade: your version is end of life and your cloud provider forced it.

Thank you Amazon!

Re:Why Does Everyone Run Ancient Postgres Versions? by mkesper on Friday October 18, 2024 @02:40AM (#41876897)
Yes, this is actually a good thing and comes with warnings beforehand.
Re:Why Does Everyone Run Ancient Postgres Versions? by throwaway918299 on Friday October 18, 2024 @07:16AM (#41878309)
I agree. It helped me completely bypass any discussion from management about “not high enough priority”. Amazon definitely did me a favour in many ways.
Re:Why Does Everyone Run Ancient Postgres Versions? by occz on Friday October 18, 2024 @02:00AM (#41876707)
Upgrading when multiple versions behind is significantly more risky than doing it when the update is relatively fresh.

Additionally, actions done frequently are less risky than actions done rarely, since you develop skills in performing that action as an organization - see high deployment frequency as a strategy of managing deployment risk.

This adds up to continuous upgrading being the least risky option in aggregate.

Re:Why Does Everyone Run Ancient Postgres Versions? by kortilla on Friday October 18, 2024 @04:20AM (#41877368)
Not if software regressions are the main concern.
Re:Why Does Everyone Run Ancient Postgres Versions? by ttfkam on Friday October 18, 2024 @11:06AM (#41880107)
Upgrading from v11 to v16 is not materially different in Postgres from v14 to v16. Same tools. Same strategies.
Re:Why Does Everyone Run Ancient Postgres Versions? by enraged_camel on Friday October 18, 2024 @11:24AM (#41880280)
We are planning to upgrade from 11 to 17 soon. Even thinking about it is giving me ulcers. Our infra provider said we actually need to upgrade to 13 first, and then to 17. They did not provide a reason.
Re:Why Does Everyone Run Ancient Postgres Versions? by Tostino on Friday October 18, 2024 @12:04PM (#41880673)
I went through a postgres 10 > 16 upgrade recently. What made it easier was just doing a test run of the upgrade process.

Did a restore to a stage environment, worked on my upgrade scripts until I was happy (deployed to VMs with ansible, so manual work to write the upgradeprocessfor me), restored again and ran the upgrade process fresh, and then tested my application, backup scripts, restores, etc. Had everything working entirely smoothly multiple times before pulling the trigger in production.

No stress at all when we did it in prod.

Re:Why Does Everyone Run Ancient Postgres Versions? by ttfkam on Friday October 18, 2024 @12:23PM (#41880884)
Yep, that was our strategy as well: just keep iterating until the script run cleanly from start to finish without errors.
Re:Why Does Everyone Run Ancient Postgres Versions? by fillest on Sunday October 20, 2024 @09:46AM (#41895330)
A personal warning about 17.0 if you use streaming replication: secondary replica leaks memory quite actively. 16.4 is OK.