E.7. Postgres Pro Standard 12.17.1
Release Date: 2023-11-15
E.7.1. Overview
This release is based onPostgreSQL 12.17 andPostgres Pro Standard 12.16.2. All improvements inherited fromPostgreSQL 12.17 are listed inPostgreSQL 12.17 Release Notes. Other major changes and enhancements are as follows:
Added new configuration parameterspgpro_build,pgpro_edition, andpgpro_version, which report thePostgres Pro source code commit ID, edition, and server version respectively.
Fixed an internal issue that could arise when an index relation was moved to a different namespace similarly to a plain relation.
Upgradedoracle_fdw to version 2.6.0.
Upgradedorafce to version 4.6.1.
Upgradedpg_filedump to version 16.0.
Upgradedpgbouncer to version 1.20.1.
Upgradedpg_probackup to version 2.6.6, which in particular improved stability of the
catchupcommand.Upgradedpgpro_controldata to version 16.1.0.
Upgradedpgpro_stats to version 1.6.3, which in particular fixed a code issue that prevented data generation for the
pgpro_stats_vacuum_tablesview. Accordingly the“Database vacuum statistics” table was not included in thepgpro_pwr report.UpgradedPTRACK to version 2.5.1 Enterprise.
E.7.2. Migration to Version 12.17.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.
While functionsnumeric_eq,numeric_ne,numeric_gt,numeric_ge,numeric_lt, andnumeric_le are actually leakproof, they were not marked as such inPostgres Pro Standard 12.1.1, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 12.2.1 repairs this issue for new installations by correcting the initial catalog data, but existing installations will still have incorrect markings unless you updatepg_proc entries for these functions. You can runpg_upgrade to upgrade your server instance to a version containing the corrected initial data, or manually correct these entries in each database of the installation using theALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq LEAKPROOF
When upgrading fromPostgres Pro versions 12.6.1 or lower, rebuild indexes containing at least one included column of type for which the collation was defined in the table.
If you are upgrading fromPostgres Pro versions 12.6.2 or lower and takePTRACK backups usingpg_probackup, retake a full backup after upgrade.