From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Robert Treat <rob(at)xzilla(dot)net> |
Cc: | Jeremy Schneider <schneider(at)ardentperf(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, 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-01 22:56:54 |
Message-ID: | Zgs7to9Dr_sdVJnR@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 13, 2024 at 02:04:16PM -0400, Robert Treat wrote:
> I tend to agree with Bruce, and major/minor seems to be the more
> common usage within the industry; iirc, debian, ubuntu, gnome, suse,
> and mariadb all use that nomenclature; and ISTR some distro's who
> release packaged versions of postgres with custom patches applied (ie
> 12.4-2 for postgres 12.4 patchlevel 2).
>
> BTW, as a reminder, we do have this statement, in bold, in the
> "upgrading" section of the versioning page:
> "We always recommend that all users run the latest available minor
> release for whatever major version is in use." There is actually
> several other phrases and wording on that page that could probably be
> propagated as replacement language in some of these other areas.
I ended up writing the attached doc patch. I found that some or our
text was overly-wordy, causing the impact of what we were trying to say
to be lessened. We might want to go farther than this patch, but I
think it is an improvement.
I also moved the <strong> text to the bottom of the section ---
previously, our <strong> wording referenced minor releases, then we
talked about major releases, and then minor releases. This gives a more
natural flow.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
Attachment | Content-Type | Size |
---|---|---|
upgrade.diff | text/x-diff | 2.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2024-04-01 23:22:38 | Re: Properly pathify the union planner |
Previous Message | Peter Geoghegan | 2024-04-01 22:33:22 | Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan |