Обсуждение: 2025-11-13 release announcement draft

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!)

Thanks!

Jonathan

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 one:

   * Do not use parallelism in hash right semi-joins.

... that wording is unclear if the "Do not use" means users/admins/etc
should not use "parallelism in hash right semi-joins", or if there's
patch(es) now applied that stop it from happening.

Any idea? :)

Regards and best wishes,

Justin Clift

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

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.

This paragraph has been used as is for many releases. I guess people who have read it many times don't really think of it anymore. And I don't personally thought of it as you do. Maybe we could juste turn the last phrase upside down :

"Please see release notes for details on potential post-upgrade steps. Users who have skipped one or more update releases may need to run additional post-update steps."

Is it really any better?

Best,

Stéphane

On 11/12/25 4:16 AM, SAS wrote:
> Le 10/11/2025 à 21:42, Justin Clift a écrit :

>> 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.
>>
> This paragraph has been used as is for many releases. I guess people who 
> have read it many times don't really think of it anymore. And I don't 
> personally thought of it as you do. Maybe we could juste turn the last 
> phrase upside down :
> 
> "Please see release notes for details on potential post-upgrade 
> steps. Users who have skipped one or more update releases may need to 
> run additional post-update steps."

Thanks for the fresh eyes on this. I thought about this a bit. For the 
current release, if there are post update steps, they are listed here, 
so I don't know if this would be confusing in that context. I've opted 
to leave the current language for now, but have been thinking on it and 
your proposed wording if we want to update it the next go-around.

Thanks!

Jonathan