E.1. Postgres Pro Standard 18.0.1#
Release Date: 2025-11-12
E.1.1. Overview#
This release is based onPostgreSQL 18 and includes all the new features introduced in PostgreSQL 18. For their detailed description, seePostgreSQL 18 Release Notes. Other major changes and enhancements are as follows:
Added the new
OLD_PASSWORD_TIMEandOLD_PASSWORD_MAXparameters for theCREATE PROFILEandALTER PROFILEcommands. These parameters are required to enable authentication with the previous password.OLD_PASSWORD_TIMEspecifies for how long the previous password can be used for authentication alongside the new one.OLD_PASSWORD_MAXspecifies the number of attempts to authenticate with the previous password before it is locked. Theoidandpassloginattemptsfields were added to thepg_role_passwordcatalog, and thepfloldpasswordtimeandpfloldpasswordmaxfields were added to thepg_profilecatalog to display information related to previous passwords.Implemented password masking in the server log by default to protect sensitive data from being revealed.
Added the newcompute_plan_id configuration parameter that allows enabling and disabling in-core computation of query plan identifiers. Also added the
plan_idfield to thepg_stat_activity view to display plan identifiers.Added the newextra_query_transformations configuration parameter that controls additional transformations of
ANYcorrelated subqueries intoLATERALjoins. This parameter replaces theenable_any_to_lateral_transformationandenable_extra_transformationsparameters that were removed.Added new values of the
PGPRO_TUNEenvironment variable used byinitdb.Inherited the vanilla implementation of automatic removal of some unnecessary table self-joins. The corresponding
enable_self_join_removalconfiguration parameter is removed; useenable_self_join_elimination instead.Removed the deprecated
pgpro_version,pgpro_edition, andpgpro_buildfunctions. Use thepgpro_version,pgpro_edition, andpgpro_build configuration parameters instead.Ended support for Ubuntu 25.04 and Debian 11.
Upgradedaqo to version 4.0 to implement optimizations that improve performance and significantly reduce overhead of query planning.
Upgradedpg_proaudit to provide the following enhancements:
Added support for logging of the following event types:
ANALYZE,DISCARD ALL,DISCARD PLANS,DISCARD SEQUENCES,DISCARD TEMP(for temporary tables),CHECKPOINT,FETCH, andMOVE.Added the new event class
MISC. This class allows logging of all events (including those mentioned above) not related to other event classes.Added a new event log field: application name.
AUTHENTICATEevents now contain the name of the initiating application alongside the connection parameters.
Upgradedpgpro_pwr to version 4.11, which provides optimizations and bug fixes. Notable changes are as follows:
Improved
take_sampletime tracking.Added a possibility to exclude server connection strings from dumps.
Added statistics on restartpoints to the reports when it is available.
Improved the behavior ofpgpro_stats similarly topro_stat_statements. The changes are:
Allow the parameterization ofSET values.
This reduces the bloat caused by
SETstatements with differing constants.Allow the parameterization of constant lists.
Upgradedorafce to version 4.16.2.
Upgradedpg_filedump to version 18.0.
Upgradedpg_probackup to version 2.8.11.
Upgradedpgpro_controldata to version 18.1.0.
Upgradedpgvector to version 0.8.1.
Upgradedtds_fdw to version 2.0.5.
Disabledonline_analyze. This module is not recommended for use with modern versions of1C. However, it can be enabled if needed.
For the list of extension modules and utilities specific toPostgres Pro Standard, as well as the main user-visible core changes as compared to vanillaPostgreSQL, seeSection 2.
E.1.2. Migration to Version 18#
You can migrate toPostgres Pro Standard 18 from the same or a previous version ofPostgreSQL (that is supported by the upgrade method chosen) and from a previous version ofPostgres Pro Standard orPostgres Pro Standard Certified. The same holds for migration toPostgres Pro Standard Certified 18. SeeSection 17.6 for the methods to upgrade your database cluster. Consult the Postgres Pro Standard support team if you experience issues during migration. Backward migration is not supported. Note that migration fromPostgres Pro Standard toPostgres Pro Standard Certified of the same major version (or vice versa) is an update betweenPostgres Pro compatible versions (seeSection 17.6 for more details).
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, make sure to install its latest available minor version and then perform a dump/restore usingpg_dumpall or use thepg_upgrade utility.
If you choose to runpg_upgrade, make sure to initialize the new database cluster with compatible parameters. In particular, pay attention to thechecksum settings in the cluster you are migrating from. Ifpg_upgrade creates any SQL files in its current directory, run these files to complete the upgrade.
When upgrading the installation from version 10 or lower, a dump/restore is recommended. In this case, you may have to resolve constraint violations manually. If this option is infeasible, you can still usepg_upgrade, but consult the Postgres Pro Standard support team since the integrity of indexes and constraints might be violated in some cases.
Note
To avoid conflicts, do not use thepostgrespro-std-18 package to install the newPostgres Pro binaries. Use the individual packages instead. In this case, server autostart needs to be enabled manually, if required. For details on the available packages, seeChapter 16.
For upgrade requirements imposed by vanillaPostgreSQL, seeSection E.2.