←back to thread

Why does everyone run ancient Postgres versions?

(neon.tech)
264 points davidgomes | 1 comments | 17 Oct 24 21:23 UTC | HN request time: 0.203s | source
Show context
Narkov ◴[18 Oct 24 11:28 UTC] No.41878370[source]▶
> Postgres 17.0 has been out for a bit

From the same blog:

> Sep 26, 2024 - Postgres 17 is Now Available

3 weeks....for a new major release...and we are asking ourselves why people haven't updated?

replies(1): >>41878489 #
jeltz ◴[18 Oct 24 11:47 UTC] No.41878489[source]▶
Yeah, upgrading to PostgreSQL 17 now would be weird unless you have some very specific feature you need in it and spent resources testing your application on the betas and rcs.
replies(1): >>41879187 #
majewsky ◴[18 Oct 24 13:19 UTC] No.41879187[source]▶
My team has upgraded several dozen databases from 16.x to 17.3. Went entirely smoothly. The thing is that we're running on a process of upgrading all dependencies every Friday, and then promoting to prod on Monday unless there are specific issues, so our definition of "would be weird" is the reverse from what you say.

(Granted, we have rather small DBs and simple applications where ON UPDATE SKIP LOCKED is about the most fancy feature we use.)

replies(2): >>41883539 #>>41895362 #
1. fillest ◴[20 Oct 24 13:52 UTC] No.41895362[source]▶
Be careful if you use streaming replication - secondary replica leaks memory on 17.0 (16.4 is fine)