Re: Just for fun: Postgres 20?

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Andreas Karlsson <andreas(at)proxel(dot)se>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, marcelo zen <mzen(at)itapua(dot)com(dot)uy>, Andreas Joseph Krogh <andreas(at)visena(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Just for fun: Postgres 20?
Date: 2020-02-15 22:40:02
Message-ID: CAA8=A7_7L7xyWoyTmdBmR+wz+e1VKZTrMnURHQZAJn495FyUNA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 14, 2020 at 7:19 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> > I also object because 20 is *my* unlucky number ...
>
> Not sure how serious Andrew is being here, but it does open up an
> important point: there are varying opinions on which numbers are unlucky.
> The idea that 13 is unlucky is Western, and maybe even only common in
> English-speaking countries. In Asia, numbers containing the digit 4
> are considered unlucky [1], and there are probably other rules in other
> cultures. If we establish a precedent that we'll skip release numbers
> for non-technical reasons, I'm afraid we'll be right back in the mess
> we sought to avoid, whereby nearly every year we had an argument about
> what the next release number would be. So let's not go there.
>
>

Yes, I was being flippant, in an attempt to make the exact point
you're making cogently but less pithily here.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2020-02-16 00:02:20 Re: explain HashAggregate to report bucket and memory stats
Previous Message Tom Lane 2020-02-15 20:25:55 Re: assert pg_class.relnatts is consistent