Re:PostgreSQL 15
by film42 on Thursday October 13, 2022 @11:15AM
(#33192173)
Corruption of database storage is the biggest fear so most upgrades are done cautiously. Historically postgres versions were released much much slower so the upgrade cadence was slower too. That said, we've been upgrading more frequently, especially since a lot of performance features are being released. So far our upgrades have been executed flawlessly for our cluster of postgres servers (~30 postgres chains each made up of 4x large dedicated servers).
[ Parent
| on HN ]
Re:PostgreSQL 15
by jeff-davis on Thursday October 13, 2022 @11:51AM
(#33192677)
Postgres has released a new major version each year for a long time.
The only change is that versions used to be X.Y.Z, and now it just used X.Y. Now, X gets incremented for every major version, so it seems like it's moving faster.
The difference is that in place upgrades aren't possible for major versions.
Re:PostgreSQL 15
by jeff-davis on Sunday October 16, 2022 @01:35PM
(#33225463)
pg_upgrade is the way to do in-place upgrade between major versions:
Jeff is right, PostgreSQL has released a new major yearly the last almost 25 years.
That would only be possible if they started with version -10!
Before version 10, the versioning scheme was different, and the first number was increased about once every five years: for example, 9.6 and 9.5 were consecutive yearly major releases. Version 7.0 was released around year 2000.