On Thu, May 21, 2026 at 10:20 AM Nikolay Samokhvalov <nik@postgres.ai> wrote:
I was thinking:
... And over last 10 years, the release cycle is pretty stable, one major version per year. So if the upcoming version were 26 instead of 19, and next year's were 27, it would be easier to understand how current this version is.
Nik
+1
There are many reasons I like this. First, it becomes obvious to EVERYONE how far behind you are in the update cycles.
Right now, if you say you are on PG 12 or PG 17 most non-technical people have no idea how far behind you are.
From my perspective, I like management asking "It's 2032... Why are we on PG 28 still?"
The only question it raises is if it should be PG 2026? because in about 1,000 years it could get confusing.
