| From: | Justin Clift <justin(at)postgresql(dot)org> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | PostgreSQL Advocacy <pgsql-advocacy(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 2025-11-13 release announcement draft |
| Date: | 2025-11-10 20:42:50 |
| Message-ID: | abc4e4e658e230993e9623fc083e9965@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SAS | 2025-11-12 09:16:03 | Re: 2025-11-13 release announcement draft |
| Previous Message | Justin Clift | 2025-11-10 20:26:13 | Re: 2025-11-13 release announcement draft |