MIME-Version: 1.0
References: 
 <CAM527d9HNDGS4wZBNK8vhRXtRX09i4UwKjvifUvSPS+P-i-1CQ@mail.gmail.com>
 <CACLU5mSnxYVf1ZkuZ4VuiREXA_42fe22+fR38y2_JJ6+WJQGyw@mail.gmail.com>
 <CAMsGm5fPUwBxgY2RGGzpEp7Sjv7VMU28vcjN+RmuWQpTWM2uRA@mail.gmail.com>
 <26422.1779465244@sss.pgh.pa.us>
 <0e41a002-ec9d-4acd-bb2c-3104c12607e3@eisentraut.org>
 <2293454.1779642239@sss.pgh.pa.us>
 <CAM527d_bY2Rcadq9sUckuVxAysU=kA2GeyG1XfRan1J2VYvDKw@mail.gmail.com>
In-Reply-To: 
 <CAM527d_bY2Rcadq9sUckuVxAysU=kA2GeyG1XfRan1J2VYvDKw@mail.gmail.com>
From: jian he <jian.universality@gmail.com>
Date: Tue, 26 May 2026 07:28:06 +0800
Message-ID: 
 <CACJufxFY8g3tUM2SGa1p+oegZnyNtg6OLqmezzumkm0vsLiKvg@mail.gmail.com>
Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?
To: Nikolay Samokhvalov <nik@postgres.ai>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter@eisentraut.org>,
	Isaac Morland <isaac.morland@gmail.com>, Kirk Wolak <wolakk@gmail.com>,
	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/CACJufxFY8g3tUM2SGa1p%2BoegZnyNtg6OLqmezzumkm0vsLiKvg%40mail.gmail.com>
Precedence: bulk

On Tue, May 26, 2026 at 6:22=E2=80=AFAM Nikolay Samokhvalov <nik@postgres.a=
i> wrote:
>
> The slip risk, the N+1 marketing-renumbering precedent, and the possibili=
ty that cadence may change (biannual or otherwise) -- all make sense.
>
> Year-tied version numbers don't fit. Let me propose something smaller tha=
t still addresses the underlying user problem =E2=80=94 knowing at a glance=
 how old a release is and when it goes EOL.
>
> I have another, much lighter proposal. In fact, two paths:
>
> 1) Docs. Add something like "Major version NN released YYYY, EOL Mon YYYY=
" explicitly on pages like:
>
> https://www.postgresql.org/docs/
> https://www.postgresql.org/docs/release/
> https://www.postgresql.org/docs/current/index.html
>

https://www.postgresql.org/docs/
After "PDF Version", add another column makes sense to me.

> https://www.postgresql.org/docs/release/
> https://www.postgresql.org/docs/current/index.html
For these two links, I'm not entirely sure where the best place to put
that information would be.