E.2. Postgres Pro Standard 17.4.1#
Release Date: 2025-03-03
E.2.1. Overview#
This release is based onPostgreSQL 17.4 andPostgres Pro Standard 17.2.1. All improvements inherited fromPostgreSQL 17.4 are listed inPostgreSQL 17.4 Release Notes. Other major changes and enhancements are as follows:
Added details, like current working directory, the
PGDATAdirectory, etc., tocrash_infooutput files.Added the increased security requirements for theCREATE PROFILE command. Now the
PASSWORD_REQUIRE_COMPLEXparameter requires characters from three different groups. Also, all characters of languages without case distinction (Hindi, Chinese, etc.) in the UTF-8 encoding are considered lowercase.Fixed an issue where
crash_infocould fail to write diagnostic files when handling a stack overflow. Previously, the signal handler ran on the same stack that had overflowed, which could prevent it from executing due to lack of available stack space. Now the handler runs on an alternate signal stack.Fixed an issue that could occur when a custom scan was used, which could cause an incorrect state of the query plan and could result in an error whenpgpro_stats was involved.
Fixed an issue where roles without explicitly set
VALID UNTILattribute and associated with a profile that hadPASSWORD_GRACE_TIME set to 0 andPASSWORD_LIFE_TIMEset toUNLIMITEDincorrectly received password expiration warnings. Now they are correctly considered valid indefinitely.Upgradedaqo to introduce the
automode, which behaves like thelearnmode but prevents memory overflow by implementing the least recently used (LRU) cache mechanism.Optimizedfasttrun to skip unnecessary truncate operations on empty temporary relations.
Upgradedmamonsu to version 3.5.11 to provide support forpgpro_stats version 1.8.
Upgradedpgbadger to version 13.0.
Upgradedpgbouncer to version 1.24.0.
Upgradedpg_portal_modify to version 0.3.5.
Upgradedpg_proaudit to provide the following enhancements and bug fixes:
Added a new event field: session user name. Now an event contains the information about both
session_userandcurrent_userattributes of an SQL session.Added support for new event classes:
ALL_DDL_NONTEMPandALL_DML_NONTEMP. The scope of these classes is limited to the objects that are not contained inpg_temp_temporary schemas.nnnFixed logging of
SELECT FOR UPDATEandSELECT FOR KEY SHAREevents asSELECT, rather thanUPDATE.
Upgradedpg_probackup to version 2.8.7, which provides the following optimizations and bug fixes:
Fixed an issue of the multi-threaded file copying technique that prevents repeated copying of one file. This issue could previously stop the backup creation under high load on the server.
Reduced the log level for“checking WAL file name” messages that are issued when the
showwith the--archiveoption is executed fromINFOtoVERBOSE.Updated the
add-instancecommand logic to make the-Doption that specifies the path to the catalog mandatory.add-instanceno longer relies on thePGDATAenvironment variable for the catalog location, but requires explicitly specifying the path to the catalog as the command option.
Upgradedpgpro_pwr to version 4.8, which provides new features and bug fixes. Notable changes are as follows:
Added tracking of extension versions installed in the cluster through a new report section.
Added a possibility to hide data for certain databases in the report. To this end, a new parameter that accepts an array of databases to be excluded was added to report generation functions.
Upgradedpgpro_stats to version 1.8.1, which provides the following bug fixes and improvements:
Fixed an issue in 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.
Implemented an optimization that lowers the locking time in some cases when copying metrics from the local memory to the shared memory.
Upgradedpg_variables. The
DISCARD ALLcommand now discards all packages and variables inpg_variables.Upgraded therum module to update an error message for an error that can occur in the case when a
SELECTquery usesORDER BY.
E.2.2. Migration to Version 17.4.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.