MIME-Version: 1.0
Date: Tue, 11 Nov 2025 06:42:50 +1000
From: Justin Clift <justin@postgresql.org>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
Subject: Re: 2025-11-13 release announcement draft
In-Reply-To: <dc8bcdf1-1402-4b42-bbaa-9a6f810660b0@postgresql.org>
References: <dc8bcdf1-1402-4b42-bbaa-9a6f810660b0@postgresql.org>
Message-ID: <abc4e4e658e230993e9623fc083e9965@postgresql.org>
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/abc4e4e658e230993e9623fc083e9965%40postgresql.org>
Precedence: bulk

On 2025-11-11 05:01, Jonathan S. Katz wrote:
> Hi,
> 
> Attached is a draft of the 2025-11-13 release announcement. Please 
> provide feedback on correctness, notable omissions no later than 
> 2025-11-13 12:00 UTC (and ideally earlier!)

With this:

   > All PostgreSQL update releases are cumulative. As with other minor 
releases,
   > users are not required to dump and reload their database or use 
`pg_upgrade`
   > in order to apply this update release; you may simply shutdown 
PostgreSQL and
   > update its binaries.
   >
   > Users who have skipped one or more update releases may need to run 
additional
   > post-update steps; please see the release notes from earlier 
versions for
   > details.

It kind of gives the impression that post-upgrade steps aren't really 
needed
unless one or more update releases have been skipped.  Not sure of 
better
wording though.

Regards and best wishes,

Justin Clift