| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Kirk Wolak <wolakk(at)gmail(dot)com> |
| Cc: | Nikolay Samokhvalov <nik(at)postgres(dot)ai>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Rename Postgres 19 to Postgres 26 (year-based)? |
| Date: | 2026-05-21 18:45:43 |
| Message-ID: | CAMsGm5fPUwBxgY2RGGzpEp7Sjv7VMU28vcjN+RmuWQpTWM2uRA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 21 May 2026 at 13:44, Kirk Wolak <wolakk(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Ashutosh Bapat | 2026-05-21 18:37:15 | Re: (SQL/PGQ) cache lookup failed for label |