public inbox for pgsql-hackers@postgresql.org  
help / color / mirror / Atom feed
From: Junwang Zhao <zhjwpku@gmail.com>
To: Nikolay Samokhvalov <nik@postgres.ai>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?
Date: Thu, 21 May 2026 23:18:54 +0800
Message-ID: <CAEG8a3Las-N6-rEc22Vr=kvHk4YJrUvH70NkC8-e+-OmmqeWjw@mail.gmail.com> (raw)
In-Reply-To: <CAM527d9HNDGS4wZBNK8vhRXtRX09i4UwKjvifUvSPS+P-i-1CQ@mail.gmail.com>
References: <CAM527d9HNDGS4wZBNK8vhRXtRX09i4UwKjvifUvSPS+P-i-1CQ@mail.gmail.com>

On Thu, May 21, 2026 at 10:20 PM 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 different versions of Postgres – this gives you perspective how old the version is.
>
> 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.

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



-- 
Regards
Junwang Zhao






reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: zhjwpku@gmail.com, nik@postgres.ai, pgsql-hackers@lists.postgresql.org
  Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?
  In-Reply-To: <CAEG8a3Las-N6-rEc22Vr=kvHk4YJrUvH70NkC8-e+-OmmqeWjw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox