public inbox for pgsql-hackers@postgresql.org  
help / color / mirror / Atom feed
From: Isaac Morland <isaac.morland@gmail.com>
To: Kirk Wolak <wolakk@gmail.com>
Cc: 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 14:45:43 -0400
Message-ID: <CAMsGm5fPUwBxgY2RGGzpEp7Sjv7VMU28vcjN+RmuWQpTWM2uRA@mail.gmail.com> (raw)
In-Reply-To: <CACLU5mSnxYVf1ZkuZ4VuiREXA_42fe22+fR38y2_JJ6+WJQGyw@mail.gmail.com>
References: <CAM527d9HNDGS4wZBNK8vhRXtRX09i4UwKjvifUvSPS+P-i-1CQ@mail.gmail.com>
	<CACLU5mSnxYVf1ZkuZ4VuiREXA_42fe22+fR38y2_JJ6+WJQGyw@mail.gmail.com>

On Thu, 21 May 2026 at 13:44, Kirk Wolak <wolakk@gmail.com> wrote:


>   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...
>

I like this because it makes it very clear that there has been a change in
numbering scheme. Skipping 7 numbers could be due to almost anything, in
the long term, but no one will think PG2026 is just 2008 versions after
PG18. Also, I agree that while most likely no one on this list will be
worrying about this in 2100, it would be nice to know that nobody has to
worry about what comes after PG99.


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: isaac.morland@gmail.com, wolakk@gmail.com, nik@postgres.ai, pgsql-hackers@lists.postgresql.org
  Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?
  In-Reply-To: <CAMsGm5fPUwBxgY2RGGzpEp7Sjv7VMU28vcjN+RmuWQpTWM2uRA@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