Re: Reports on obsolete Postgres versions

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Robert Treat <rob(at)xzilla(dot)net>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, Michael Banck <mbanck(at)gmx(dot)net>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reports on obsolete Postgres versions
Date: 2024-04-02 20:48:28
Message-ID: 4DB71528-0135-408C-B3F1-005D4A81F219@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 2 Apr 2024, at 22:46, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Tue, Apr 2, 2024 at 11:34:46AM +0200, Magnus Hagander wrote:

>> I do like the term "current" better. It conveys (at least a bit) that we
>> really consider all the older ones to be, well, obsolete. The difference
>> "current vs obsolete" is stronger than "latest vs not quite latest".
>
> Okay, I changed "superseded" to "old", and changed "latest" to
> "current", patch attached.

+1, LGTM

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2024-04-02 20:54:28 Re: Combine Prune and Freeze records emitted by vacuum
Previous Message Bruce Momjian 2024-04-02 20:46:58 Re: Reports on obsolete Postgres versions