Release Date: 2024-12-03
This release is based on PostgreSQL 17.2 and Postgres Pro Standard 17.0.1. All improvements inherited from PostgreSQL 17.2 are listed in PostgreSQL 17.2 Release Notes. Other major changes and enhancements are as follows:
Added the ability to form the MergeAppend operation
instead of Append, which allows omitting additional
sorting needed to ensure that the data is in fact sorted. Now
MergeAppend is formed specifying the columns to sort by.
The new ability applies only when the enable_appendorpath
option is set to ON.
Fixed an issue that could occur when certain queries were
processing the PLAN clause of the
JSON_TABLE function. Previously, the data
returned by the NESTED PATH clause 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 TO command when using the
online_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 the
enable_appendorpath option set to ON.
Added support for Ubuntu 24.10.
Upgraded mamonsu to version 3.5.9, which provides optimizations and bug fixes. Notable changes are as follows:
Added support for systems where setuptools version greater than 67.7.2 is installed.
Ended the use of dotted user:group specification
at the RPM pre-install stage.
Upgraded pg_portal_modify to version 0.3.4.
Upgraded pg_probackup to version 2.8.5, which provides the following optimizations and bug fixes:
Enabled the output of the version command in the JSON
format using --format=json.
Added the --all option to the amcheck
command, which allows performing all the checks in a single command.
Added support for the include parameter in the configuration
file. The contents of the file specified in include
gets 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-threads and --validate-threads
option, respectively.
Changed the priority of setting PGDATA and
BACKUP_PATH. Now the values from the command-line
options take precedence.
Added validation of WAL files for backups to be merged by the
merge command.
An error message that was issued when the validate
command run with the --wal option found an archive in the
DEGRADED status 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.
Upgraded pgpro_stats to provide the following optimizations and bug fixes:
Implemented an optimization that lowers the locking time in some cases when copying metrics from the local memory to the shared memory.
Fixed an issue that could occur during session tracing and cause errors “could not write file ""pg_stat/pgpro_stats_filters.trace.tmp"": No such file or directory”. Concurrent writing from different sessions to a trace file is fixed now, so processes can write to the trace file in parallel without collisions.
Upgraded PTRACK to prevent possible issues with PTRACK
backups by setting the ptrack.map file for automatic
deletion when PTRACK is disabled.
If you are upgrading from Postgres Pro Standard based on the same PostgreSQL major version, it is enough to install the new version into your current installation directory.
ABI versions may change between minor releases of
Postgres Pro. If this is the case, and you see
the ABI mismatch error when trying to run your
extension, make sure to install a new version of the extension
supplied with a new release of Postgres Pro,
or recompile your third-party extension to be able to use it with the
current version of Postgres Pro.
To migrate from PostgreSQL or a Postgres Pro Standard release based on a previous PostgreSQL major version, see the instructions in Postgres Pro Standard 17.0.1 Release Notes.