The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23. This release fixes 25 bugs reported over the last several months.
This is the final release of PostgreSQL 10. PostgreSQL 10 will no longer receive security and bug fixes. If you are running PostgreSQL 10 in a production environment, we suggest that you make plans to upgrade.
For the full list of changes, please review the release notes.
This update fixes over 25 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 15. Some of these issues may also affect other supported versions of PostgreSQL.
Included in this release:
INSERTstatements that include multi-row
VALUESclauses with a
_RETURNthat are not
MERGEon a partitioned table that has foreign-table partitions.
ALTER TABLE ... ATTACH PARTITION, where previously incorrect or duplicate constraints could be built.
psql -cnow exits with a nonzero status if the query is canceled.
This release also updates time zone data files to use tzdata release 2022f. This includes DST law changes in Chile, Fiji, Iran, Jordan, Mexico, Palestine, and Syria, plus historical corrections for Chile, Crimea, Iran, and Mexico.
There are several other changes to note in the tzdata 2022f release that may change the display for pre-1970 timestamps. For a detailed explanation, please review the release notes.
For the full list of changes available, please review the release notes.
PostgreSQL 10.23 is the final release of PostgreSQL 10. If you are running PostgreSQL 10 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information.
All PostgreSQL update releases are cumulative. As with other minor releases,
users are not required to dump and reload their database or use
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 for earlier versions for details.
For more details, please see the release notes.