public inbox for pgsql-advocacy@postgresql.org
help / color / mirror / Atom feed2025-11-13 release announcement draft
5+ messages / 3 participants
[nested] [flat]
* 2025-11-13 release announcement draft
@ 2025-11-10 19:01 Jonathan S. Katz <jkatz@postgresql.org>
0 siblings, 2 replies; 5+ messages in thread
From: Jonathan S. Katz @ 2025-11-10 19:01 UTC (permalink / raw)
To: PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
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
Attachments:
[text/x-markdown] 20251113updaterelease.md (4.4K, 2-20251113updaterelease.md)
download | inline:
The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 18.1, 17.7, 16.11, 15.15, 14.20, and
13.23. This release fixes over 50 bugs reported over the last several months.
If you previously created a BRIN index using the `numeric_minmax_multi_ops`
operator class, please see the "Updating" section for additional instructions
after upgrading your instance.
For the full list of changes, please review the [release
notes](https://www.postgresql.org/docs/release/).
PostgreSQL 13 EOL Notice
------------------------
**This is the final release of PostgreSQL 13**. PostgreSQL 13 is now end-of-life
and will no longer receive security and bug fixes. If you are
running PostgreSQL 13 in a production environment, we suggest that you make
plans to upgrade to a newer, supported version of PostgreSQL. Please see our
[versioning policy](https://www.postgresql.org/support/versioning/) for more
information.
Bug Fixes and Improvements
--------------------------
This update fixes over 50 bugs that were reported in the last several
months. The issues listed below affect PostgreSQL 18. Some of these issues may
also affect other supported versions of PostgreSQL.
* Do not use parallelism in hash right semi-joins.
* Avoid possible out-of-memory failures during parallel GIN index build.
* Several fixes for BRIN indexes.
* Fixes for crashes related to partitioned tables, including one occurring during a recheck.
* Avoid duplicating hash partition constraints during `DETACH CONCURRENTLY`, which previously caused issues during dump/restore or if a parent table is dropped after the `DETACH`.
* Disallow [generated columns](https://www.postgresql.org/docs/current/ddl-generated-columns.html) in partition keys and in [`COPY ... FROM ... WHERE`](https://www.postgresql.org/docs/current/sql-copy.html) clauses.
* Fix incorrect reporting of replication lag in [`pg_stat_replication`](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-REPLICATION-VIEW) view.
* Avoid failures when [`synchronized_standby_slots`](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-SYNCHRONIZED-STANDBY-SLOTS) references nonexistent replication slots.
* Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source.
* Avoid unnecessary invalidation of logical replication slots.
* Correctly handle `GROUP BY DISTINCT` in [PL/pgSQL](https://www.postgresql.org/docs/current/plpgsql.html) assignment statements.
* Avoid leaking memory when handling a SQL error within [PL/Python](https://www.postgresql.org/docs/current/plpython.html).
* Fix how libpq handles socket-related errors on Windows within its [GSSAPI](https://www.postgresql.org/docs/current/gssapi-auth.html) logic.
* Fix dumping of non-inherited `NOT NULL` constraints on inherited table columns.
* Ensure consistent ordering of foreign key constraints in the output of [`pg_dump`](https://www.postgresql.org/docs/current/app-pgdump.html).
* Several fixes for [`pgbench`](https://www.postgresql.org/docs/current/pgbench.html) error handling and reporting.
* Fix memory leak in [`pg_combinebackup`](https://www.postgresql.org/docs/current/app-pgcombinebackup.html).
* Allow nonsuperusers with `SELECT` privileges on a table to use [`pg_prewarm`](https://www.postgresql.org/docs/current/pgprewarm.html) to prewarm indexes on that table.
Updating
--------
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.
For more details, please see the [release
notes](https://www.postgresql.org/docs/release/).
Links
-----
* [Download](https://www.postgresql.org/download/)
* [Release Notes](https://www.postgresql.org/docs/release/)
* [Security](https://www.postgresql.org/support/security/)
* [Versioning Policy](https://www.postgresql.org/support/versioning/)
* [Submit a Bug](https://www.postgresql.org/account/submitbug/)
* [Donate](https://www.postgresql.org/about/donate/)
If you have corrections or suggestions for this release announcement, please
send them to the _pgsql-www@lists.postgresql.org_ public [mailing
list](https://www.postgresql.org/list/).
[application/pgp-signature] OpenPGP_signature.asc (840B, 3-OpenPGP_signature.asc)
download
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: 2025-11-13 release announcement draft
@ 2025-11-10 20:26 Justin Clift <justin@postgresql.org>
parent: Jonathan S. Katz <jkatz@postgresql.org>
1 sibling, 0 replies; 5+ messages in thread
From: Justin Clift @ 2025-11-10 20:26 UTC (permalink / raw)
To: Jonathan S. Katz <jkatz@postgresql.org>; +Cc: PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: 2025-11-13 release announcement draft
@ 2025-11-10 20:42 Justin Clift <justin@postgresql.org>
parent: Jonathan S. Katz <jkatz@postgresql.org>
1 sibling, 1 reply; 5+ messages in thread
From: Justin Clift @ 2025-11-10 20:42 UTC (permalink / raw)
To: Jonathan S. Katz <jkatz@postgresql.org>; +Cc: PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: 2025-11-13 release announcement draft
@ 2025-11-12 09:16 SAS <sas.postgresql@gmail.com>
parent: Justin Clift <justin@postgresql.org>
0 siblings, 1 reply; 5+ messages in thread
From: SAS @ 2025-11-12 09:16 UTC (permalink / raw)
To: pgsql-advocacy@lists.postgresql.org
Le 10/11/2025 à 21:42, Justin Clift a écrit :
> 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
--
Dr Stéphane Schildknecht
Contact régional PostgreSQL pour l'Europe francophone
+33 617 11 37 42
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: 2025-11-13 release announcement draft
@ 2025-11-13 14:17 Jonathan S. Katz <jkatz@postgresql.org>
parent: SAS <sas.postgresql@gmail.com>
0 siblings, 0 replies; 5+ messages in thread
From: Jonathan S. Katz @ 2025-11-13 14:17 UTC (permalink / raw)
To: SAS <sas.postgresql@gmail.com>; pgsql-advocacy@lists.postgresql.org
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
Attachments:
[application/pgp-signature] OpenPGP_signature.asc (840B, 2-OpenPGP_signature.asc)
download
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2025-11-13 14:17 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-11-10 19:01 2025-11-13 release announcement draft Jonathan S. Katz <jkatz@postgresql.org>
2025-11-10 20:26 ` Justin Clift <justin@postgresql.org>
2025-11-10 20:42 ` Justin Clift <justin@postgresql.org>
2025-11-12 09:16 ` SAS <sas.postgresql@gmail.com>
2025-11-13 14:17 ` Jonathan S. Katz <jkatz@postgresql.org>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox