E.1. Postgres Pro Standard 15.18.1
Date: 2026-05-28
E.1.1. Overview
This release is based on PostgreSQL 15.18 and Postgres Pro Standard 15.17.1. All improvements inherited from PostgreSQL 15.18 are listed in PostgreSQL 15.18 Release Notes. Other major changes and enhancements are as follows:
Added the log_parameter_types configuration parameter that controls whether each bind parameter value for a prepared statement in log messages is prefixed with its data type. For example,
[integer] $1 = '42'.Restricted changes to the hba_file configuration parameter in the certified edition of Postgres Pro Standard. For enhanced security, it is also recommended to use pg_integrity_check, which automatically verifies the integrity of critical files before server startup.
Added build IDs of executables and shared libraries to crash_info output files.
Fixed an issue with estimating the number of join rows when the enable_compound_index_stats parameter is set to
on.Removed the functionality of the optimizer for adding
Index Only Scanplan nodes belowAppendnodes that are generated forORclauses if the enable_appendorpath parameter is set toon. This functionality could cause incorrect query execution plans and resulting data.Upgraded aqo to fix a segmentation fault that could occur after aborting a nested autonomous transaction for which aqo was used. Now aqo checks the nesting level of autonomous transactions and does not clear its local cache when aborting nested transactions.
Upgraded orafce to version 4.16.5.
Upgraded pg_query_state to fix an issue that could cause the module to hang while waiting for the response from the backend that executes the investigated query.
Upgraded pg_proaudit to provide the following enhancements and bug fixes:
Added the pg_proaudit.log_file_mode configuration parameter that specifies permissions for new event log files created by pg_proaudit. Note that regardless of this parameter, the server owner always retains access to the log files.
Added a new event field for all types of events logged in CSV files and syslog: IP address of the event source. Previously, this field was displayed only for
AUTHENTICATEevents logged in the CEF format.Extended the use of the pg_proaudit.log_rows configuration parameter that enables or disables logging of the number of rows affected by an SQL command. Now the number of affected rows is written for all formats of logged events.
Added validation of the unique ID of the event (UUID) to avoid invalid memory access.
Fixed an issue with incorrect filling of the
dstfield for events logged in CEF format.Fixed an issue with excessive memory usage when processing
DISCONNECTevents. Previously, a hash table sized proportionally to max_connections caused unnecessary memory consumption when the value was large. The data is now stored more efficiently.Fixed a parser error in pg_proaudit. Previously, pg_proaudit left some characters unescaped when logging events in the CEF format. Now, symbols are escaped correctly in accordance with the CEF specification.
Upgraded pg_probackup to version 2.8.14 to provide the following improvements and bug fixes:
Added support for absolute paths in the
--wal-file-pathoption.Fixed incremental backups in
PAGEmode with the--streamoption. With this combination of parameters, WAL files are now correctly saved both inside the backup and in a separate archive.
Upgraded pgpro_bindump to provide the following improvements and bug fixes:
Added support for the
--exclude-pathoption to exclude specific files or directories from backup inPROmode.Optimized the backup performance by excluding temporary files of the
postmasterprocess.
Upgraded pgpro_datactl to version 1.5.
Upgraded pgpro_pwr to version 4.13, which adds support for cluster-wide Postgres Pro Shardman statistics and provides optimizations and bug fixes.
Upgraded pgpro_stats to fix excessive memory consumption by a query that used pgpro_stats with
pgpro_stats.trackset toall. With this setting, a function that assigned plan IDs was called multiple times, and the accumulated memory was not optimally released.Upgraded pgpro_tune to provide the following enhancements:
Improved the utility output to include the used preset and display the correct format of date and time when configuration parameters were applied.
Updated presets to improve performance of Postgres Pro.
Fixed an issue where the shared_buffers configuration parameter was calculated incorrectly when using initdb with the enabled pgpro_tune extension. This issue could cause the command to run slower.
Upgraded pg_variables to support Postgres Pro/ PostgreSQL 18.
Upgraded pgvector to version 0.8.2.
Upgraded rum to improve performance of RUM index search using the index operators
<=|and|=>when the order_by_attach index storage parameter is set totrue.
E.1.2. Migration to Version 15.18.1
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.
If you take backups using pg_probackup and you have previously upgraded it to version 2.8.0 or 2.8.1, make sure to upgrade it to version 2.8.2 or higher and retake a full backup after upgrade, since backups taken using those versions might be corrupted. If you suspect that your backups taken with versions 2.8.0 or 2.8.1 may be corrupted, you can validate them using version 2.8.2.
Starting from Postgres Pro Standard 15.5.1, the privileges of CREATEROLE are restricted, and modification of other roles requires the role requesting the change to have the ADMIN OPTION permission.
When upgrading to Postgres Pro versions starting with 15.3.1, make sure to upgrade pg_probackup to version 2.6.3 or higher since lower versions are incompatible with these Postgres Pro versions.
To migrate from PostgreSQL or a Postgres Pro Standard release based on a previous PostgreSQL major version, see the instructions in Postgres Pro Standard 15.0.1 Release Notes.