Re: Reports on obsolete Postgres versions

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: 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 07:24:04
Message-ID: 7C1994C7-8316-40C0-931F-FE2DBEEF2FC2@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 2 Apr 2024, at 00:56, Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> 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.

Agreed, this is an good incremental improvement over what we have.

> I also moved the <strong> text to the bottom of the section

+1

A few small comments:

+considers performing minor upgrades to be less risky than continuing to
+run superseded minor versions.</em>

I think "superseded minor versions" could be unnecessarily complicated for
non-native speakers, I consider myself fairly used to reading english but still
had to spend a few extra (brain)cycles parsing the meaning of it in this
context.

+ We recommend that users always run the latest minor release associated

Or perhaps "current minor release" which is the term we use in the table below
on the same page?

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2024-04-02 07:38:12 Re: Improve tab completion for ALTER DEFAULT PRIVILEGE and ALTER TABLE
Previous Message Nazir Bilal Yavuz 2024-04-02 07:23:55 Re: Use streaming read API in ANALYZE