E.3. Postgres Pro Standard 17.2.1#
Release Date: 2024-12-03
E.3.1. Overview#
This release is based onPostgreSQL 17.2 andPostgres Pro Standard 17.0.1. All improvements inherited fromPostgreSQL 17.2 are listed inPostgreSQL 17.2 Release Notes. Other major changes and enhancements are as follows:
Added the ability to form the
MergeAppendoperation instead ofAppend, which allows omitting additional sorting needed to ensure that the data is in fact sorted. NowMergeAppendis formed specifying the columns to sort by. The new ability applies only when theenable_appendorpath option is set toON.Fixed an issue that could occur when certain queries were processing the
PLANclause of theJSON_TABLEfunction. Previously, the data returned by theNESTED PATHclause could be incorrectly joined with the view being created. As a result, such queries could fail to return the lines awaited or return extra lines.Fixed a segmentation fault, which could occur while executing the
COPY TOcommand when using theonline_analyze module.Fixed an issue that could slow down query execution. The reason was that the optimizer selected a suboptimal index due to the lack of its cost estimation after removing redundant clauses with theenable_appendorpath option set to
ON.Added support for Ubuntu 24.10.
Upgradedmamonsu to version 3.5.9, which provides optimizations and bug fixes. Notable changes are as follows:
Added support for systems wheresetuptools version greater than 67.7.2 is installed.
Ended the use of dotted
user:groupspecification at the RPM pre-install stage.
Upgradedpg_portal_modify to version 0.3.4.
Upgradedpg_probackup to version 2.8.5, which provides the following optimizations and bug fixes:
Enabled the output of the
versioncommand in the JSON format using--format=json.Added the
--alloption to theamcheckcommand, which allows performing all the checks in a single command.Added support for the
includeparameter in the configuration file. The contents of the file specified inincludegets added to the configuration file instead of this parameter.Added a possibility to specify an individual number of threads for execution of a backup and its subsequent validation by specifying the
--backup-threadsand--validate-threadsoption, respectively.Changed the priority of setting
PGDATAandBACKUP_PATH. Now the values from the command-line options take precedence.Added validation of WAL files for backups to be merged by the
mergecommand.An error message that was issued when the
validatecommand run with the--waloption found an archive in theDEGRADEDstatus has been replaced with a warning since backups in this status do not affect the restore correctness as a whole.Fixed an issue that could occur if the command line was too long.
Fixed an issue that could occur during validation or restore when the PITR from a previous timeline was performed.
UpgradedPTRACK to prevent possible issues with PTRACK backups by setting the
ptrack.mapfile for automatic deletion when PTRACK is disabled.
E.3.2. Migration to Version 17.2.1#
If you are upgrading fromPostgres Pro Standard based on the samePostgreSQL major version, it is enough to install the new version into your current installation directory.
ABI versions may change between minor releases ofPostgres Pro. If this is the case, and you see theABI mismatch error when trying to run your extension, make sure to install a new version of the extension supplied with a new release ofPostgres Pro, or recompile your third-party extension to be able to use it with the current version ofPostgres Pro.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 17.0.1 Release Notes.