MIME-Version: 1.0
References: 
 <CAM527d9HNDGS4wZBNK8vhRXtRX09i4UwKjvifUvSPS+P-i-1CQ@mail.gmail.com>
In-Reply-To: 
 <CAM527d9HNDGS4wZBNK8vhRXtRX09i4UwKjvifUvSPS+P-i-1CQ@mail.gmail.com>
From: Junwang Zhao <zhjwpku@gmail.com>
Date: Thu, 21 May 2026 23:18:54 +0800
Message-ID: 
 <CAEG8a3Las-N6-rEc22Vr=kvHk4YJrUvH70NkC8-e+-OmmqeWjw@mail.gmail.com>
Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?
To: Nikolay Samokhvalov <nik@postgres.ai>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAEG8a3Las-N6-rEc22Vr%3DkvHk4YJrUvH70NkC8-e%2B-OmmqeWjw%40mail.gmail.com>
Precedence: bulk

On Thu, May 21, 2026 at 10:20=E2=80=AFPM Nikolay Samokhvalov <nik@postgres.=
ai> wrote:
>
> I was thinking:
>
> in my mind, Postgres 9.6 was associated with 2016, and "6" at the end of =
both the version and the year always helped me memorize the release year.
>
> Memorizing is important when you deal with many databases running differe=
nt versions of Postgres =E2=80=93 this gives you perspective how old the ve=
rsion is.
>
> And over last 10 years, the release cycle is pretty stable, one major ver=
sion per year. So if the upcoming version were 26 instead of 19, and next y=
ear's were 27, it would be easier to understand how current this version is=
.

Interesting. I think macOS has gone through a similar evolution, macOS
Tahoe (Version 26.5), released in May 2025. We could also give each
major release a name, which sounds pretty interesting to me.

Ubuntu uses a year-based versioning scheme and gives each LTS release
a name, while Debian does not use year-based versions but still
assigns a name to every release.

>
> Nik


--=20
Regards
Junwang Zhao