MIME-Version: 1.0
References: 
 <CAM527d9HNDGS4wZBNK8vhRXtRX09i4UwKjvifUvSPS+P-i-1CQ@mail.gmail.com>
In-Reply-To: 
 <CAM527d9HNDGS4wZBNK8vhRXtRX09i4UwKjvifUvSPS+P-i-1CQ@mail.gmail.com>
From: Kirk Wolak <wolakk@gmail.com>
Date: Thu, 21 May 2026 13:44:08 -0400
Message-ID: 
 <CACLU5mSnxYVf1ZkuZ4VuiREXA_42fe22+fR38y2_JJ6+WJQGyw@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: multipart/alternative; boundary="0000000000003fd2c90652577720"
Archived-At: 
 <https://www.postgresql.org/message-id/CACLU5mSnxYVf1ZkuZ4VuiREXA_42fe22%2BfR38y2_JJ6%2BWJQGyw%40mail.gmail.com>
Precedence: bulk

--0000000000003fd2c90652577720
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, May 21, 2026 at 10:20=E2=80=AFAM 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.
And I know the PG crowd likes to think ahead...

Kirk Out!

--0000000000003fd2c90652577720
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"col=
or:rgb(0,0,0)"><span style=3D"color:rgb(34,34,34)">On Thu, May 21, 2026 at =
10:20=E2=80=AFAM Nikolay Samokhvalov &lt;<a href=3D"mailto:nik@postgres.ai"=
>nik@postgres.ai</a>&gt; wrote:</span></div></div><div class=3D"gmail_quote=
 gmail_quote_container"><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div dir=3D"ltr"><div>I was thinking:</div><div><div class=3D"gmail_default"=
 style=3D"color:rgb(0,0,0)">...=C2=A0<span style=3D"color:rgb(34,34,34)">An=
d over last 10 years, the release=C2=A0cycle is pretty stable, one major ve=
rsion per year. So if the upcoming version were 26 instead of 19, and next =
year&#39;s were 27, it would be easier to understand how=C2=A0current=C2=A0=
this version is.</span></div></div><div><div dir=3D"ltr" class=3D"gmail_sig=
nature"><div dir=3D"ltr"><div><br></div><div>Nik</div></div></div></div></d=
iv></blockquote><div><span class=3D"gmail_default" style=3D"color:rgb(0,0,0=
)">+1</span></div><div><br></div><div class=3D"gmail_default" style=3D"colo=
r:rgb(0,0,0)">=C2=A0 There are many reasons I like this.=C2=A0 First, it be=
comes obvious to EVERYONE how far behind you are in the update cycles.</div=
><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)">Right now, if you =
say you are on PG 12 or PG 17 most non-technical people have no idea how fa=
r behind you are.</div><div class=3D"gmail_default" style=3D"color:rgb(0,0,=
0)"><br></div><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)">=C2=
=A0 From my perspective, I like management asking &quot;It&#39;s 2032...=C2=
=A0 Why are we on PG 28 still?&quot;</div><div class=3D"gmail_default" styl=
e=3D"color:rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D"colo=
r:rgb(0,0,0)">=C2=A0 The only question it raises is if it should be PG 2026=
?=C2=A0 =C2=A0because in about 1,000 years it could get confusing.</div><di=
v class=3D"gmail_default" style=3D"color:rgb(0,0,0)">And I know the PG crow=
d likes to think ahead...</div><div class=3D"gmail_default" style=3D"color:=
rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D"color:rgb(0,0,0=
)">Kirk Out!</div></div></div>

--0000000000003fd2c90652577720--