On Tue, Jun 2, 2020 at 2:45 PM Robert Haas wrote:
> On Mon, Jun 1, 2020 at 3:20 PM Tom Lane wrote:
> > Robert Haas writes:
> > > As has already been pointed out, it could definitely happen, but we
> > > could solve that by just using a longer version number, say, including
> > > the month and,
On Mon, Jun 1, 2020 at 3:20 PM Tom Lane wrote:
> Robert Haas writes:
> > As has already been pointed out, it could definitely happen, but we
> > could solve that by just using a longer version number, say, including
> > the month and, in case we ever do multiple major releases in the same
> >
Robert Haas writes:
> As has already been pointed out, it could definitely happen, but we
> could solve that by just using a longer version number, say, including
> the month and, in case we ever do multiple major releases in the same
> month, also the day. In fact, we might as well take it one
On Wed, Feb 12, 2020 at 11:25 AM Juan José Santamaría Flecha
wrote:
> On Wed, Feb 12, 2020 at 3:47 PM Tom Lane wrote:
>> Yeah; I don't think it's *that* unlikely for it to happen again. But
>> my own principal concern about this mirrors what somebody else already
>> pointed out: the
On 26.05.2020 3:55, Bruce Momjian wrote:
On Mon, May 25, 2020 at 11:05:09AM +0200, Jiří Fejfar wrote:
On 15.02.2020 1:18, Tom Lane wrote:
The idea that 13 is unlucky is Western, and maybe even only common in
English-speaking countries.
Number 13 (especially Friday 13) is also considered
On Mon, May 25, 2020 at 11:05:09AM +0200, Jiří Fejfar wrote:
> On 15.02.2020 1:18, Tom Lane wrote:
> > The idea that 13 is unlucky is Western, and maybe even only common in
> > English-speaking countries.
>
> Number 13 (especially Friday 13) is also considered unlucky In Czech
> republic (central
Please don't take personal but when you open a discussion like that on number
13 then you are doing something very christian centric and forget the rest of
the world. As there are more cultural spheres than the christian one on this
planet can you please elaborate the next number which is
On 15.02.2020 1:18, Tom Lane wrote:
The idea that 13 is unlucky is Western, and maybe even only common in
English-speaking countries.
Number 13 (especially Friday 13) is also considered unlucky In Czech
republic (central Europe, Slavic language).
--
Jiří.
On Wed, Feb 12, 2020 at 10:38:19PM +0100, Michael Banck wrote:
> Hi,
>
> On Wed, Feb 12, 2020 at 02:52:53PM +0100, Andreas Karlsson wrote:
> > On 2/12/20 12:07 AM, Alvaro Herrera wrote:
> > > marcelo zen escribió:
> > > > I'd rather have releases being made when the software is ready and
> > > >
On Fri, Feb 14, 2020 at 7:19 PM Tom Lane wrote:
>
> Andrew Dunstan 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
On Thu, Feb 13, 2020 at 1:34 PM Andrew Dunstan
wrote:
> I also object because 20 is *my* unlucky number ...
I don't think we're going to do this, so you don't have to worry on that score.
--
Peter Geoghegan
On Fri, Feb 14, 2020 at 4:19 PM Tom Lane wrote:
> 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.
I
Andrew Dunstan 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
On Thu, Feb 13, 2020 at 2:14 PM Michael Paquier wrote:
>
> On Wed, Feb 12, 2020 at 09:46:48AM -0500, Tom Lane wrote:
> > Yeah; I don't think it's *that* unlikely for it to happen again. But
> > my own principal concern about this mirrors what somebody else already
> > pointed out: the
On Wed, Feb 12, 2020 at 09:46:48AM -0500, Tom Lane wrote:
> Yeah; I don't think it's *that* unlikely for it to happen again. But
> my own principal concern about this mirrors what somebody else already
> pointed out: the one-major-release-per-year schedule is not engraved on
> any stone tablets.
Hi,
On Wed, Feb 12, 2020 at 02:52:53PM +0100, Andreas Karlsson wrote:
> On 2/12/20 12:07 AM, Alvaro Herrera wrote:
> > marcelo zen escribió:
> > > I'd rather have releases being made when the software is ready and
> > > not when the calendar year mandates it. It seems like a terrible
> > > idea.
On 12/02/2020 21:10, David Fetter wrote:
> On Wed, Feb 12, 2020 at 05:25:15PM +0100, Juan José Santamaría Flecha wrote:
>> On Wed, Feb 12, 2020 at 3:47 PM Tom Lane wrote:
>>
>>>
>>> Yeah; I don't think it's *that* unlikely for it to happen again. But
>>> my own principal concern about this
On Wed, Feb 12, 2020 at 05:25:15PM +0100, Juan José Santamaría Flecha wrote:
> On Wed, Feb 12, 2020 at 3:47 PM Tom Lane wrote:
>
> >
> > Yeah; I don't think it's *that* unlikely for it to happen again. But
> > my own principal concern about this mirrors what somebody else already
> > pointed
On Wed, 12 Feb 2020 at 14:58, Laurenz Albe wrote:
> On Wed, 2020-02-12 at 12:32 -0500, Christopher Browne wrote:
> > All said, I think there's some merit to avoiding a PostgreSQL 13
> release, because
> > there's enough superstition out there about the infamous "number 13."
>
> It would make me
On Wed, 2020-02-12 at 12:32 -0500, Christopher Browne wrote:
> All said, I think there's some merit to avoiding a PostgreSQL 13 release,
> because
> there's enough superstition out there about the infamous "number 13."
It would make me sad if the project kotowed to superstition like Oracle did.
On Wed, 12 Feb 2020 at 08:28, Alvaro Herrera
wrote:
> marcelo zen escribió:
> > I'd rather have releases being made when the software is ready and not
> when
> > the calendar year mandates it.
> > It seems like a terrible idea.
>
> But we do actually release on calendar year. While it seems not
On Wed, Feb 12, 2020 at 3:47 PM Tom Lane wrote:
>
> Yeah; I don't think it's *that* unlikely for it to happen again. But
> my own principal concern about this mirrors what somebody else already
> pointed out: the one-major-release-per-year schedule is not engraved on
> any stone tablets. So I
Andreas Karlsson escribió:
> On 2/12/20 12:07 AM, Alvaro Herrera wrote:
> > marcelo zen escribió:
> > > I'd rather have releases being made when the software is ready and not
> > > when
> > > the calendar year mandates it.
> > > It seems like a terrible idea.
> >
> > But we do actually release
Andreas Karlsson writes:
> On 2/12/20 12:07 AM, Alvaro Herrera wrote:
>> But we do actually release on calendar year. While it seems not
>> unreasonable that we might fail to ship in time, that would likely lead
>> to one month, two months of delay. Four months? I don't think anybody
>> even
On 2/12/20 12:07 AM, Alvaro Herrera wrote:
marcelo zen escribió:
I'd rather have releases being made when the software is ready and not when
the calendar year mandates it.
It seems like a terrible idea.
But we do actually release on calendar year. While it seems not
unreasonable that we
marcelo zen escribió:
> I'd rather have releases being made when the software is ready and not when
> the calendar year mandates it.
> It seems like a terrible idea.
But we do actually release on calendar year. While it seems not
unreasonable that we might fail to ship in time, that would likely
I'd rather have releases being made when the software is ready and not when
the calendar year mandates it.
It seems like a terrible idea.
On Tue, 11 Feb 2020 at 14:03, Andreas Joseph Krogh
wrote:
> This project already tried that:
>
>
>
> From: Jose Luis Tallon
>
> > Musing some other date-related things I stumbled upon the thought
> > that naming the upcoming release PostgreSQL 20 might be preferrable to
> > the current/expected "PostgreSQL 13".
>
> +1
>
> Users can easily know how old/new the release is that they are
And nobody is asking about all the "missing" versions like in a big red
superstitious database.
Am Montag, 10. Februar 2020, 00:45:02 MEZ hat tsunakawa.ta...@fujitsu.com
Folgendes geschrieben:
From: Jose Luis Tallon
> Musing some other date-related things I stumbled upon the
From: Jose Luis Tallon
> Musing some other date-related things I stumbled upon the thought
> that naming the upcoming release PostgreSQL 20 might be preferrable to
> the current/expected "PostgreSQL 13".
+1
Users can easily know how old/new the release is that they are using.
Regards
Jose Luis Tallon writes:
> Musing some other date-related things I stumbled upon the thought
> that naming the upcoming release PostgreSQL 20 might be preferrable to
> the current/expected "PostgreSQL 13".
Sorry, but it's not April 1st yet.
regards, tom lane
On 09/02/2020 19:28, Jose Luis Tallon wrote:
> * Simplified supportability assessment: PostgreSQL 20, released in
> 2020, would be supported until the release of PostgreSQL 25 (late 2025
> if release cadence is kept as today). Simple and straightforward.
How would you handle multiple releases
32 matches
Mail list logo
