From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Reports on obsolete Postgres versions |
Date: | 2024-03-12 01:37:56 |
Message-ID: | 20240312013756.GB1787866@nathanxps13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 11, 2024 at 05:17:13PM -0400, Bruce Momjian wrote:
> On Mon, Mar 11, 2024 at 04:12:04PM -0500, Nathan Bossart wrote:
>> I've read that the use of the term "minor release" can be confusing. While
>> the versioning page clearly describes what is eligible for a minor release,
>> not everyone reads it, so I suspect that many folks think there are new
>> features, etc. in minor releases. I think a "minor release" of Postgres is
>> more similar to what other projects would call a "patch version."
>
> Well, we do say:
>
> While upgrading will always contain some level of risk, PostgreSQL
> minor releases fix only frequently-encountered bugs, security issues,
> and data corruption problems to reduce the risk associated with
> upgrading. For minor releases, the community considers not upgrading to
> be riskier than upgrading.
>
> but that is far down the page. Do we need to improve this?
I think making that note more visible would certainly be an improvement.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2024-03-12 01:43:33 | Re: WIP Incremental JSON Parser |
Previous Message | Nathan Bossart | 2024-03-12 01:34:36 | Re: Popcount optimization using AVX512 |