E.3. Postgres Pro Standard 12.17.1
Release Date: 2023-11-15
E.3.1. Overview
This release is based on PostgreSQL 12.17 and Postgres Pro Standard 12.16.2. All improvements inherited from PostgreSQL 12.17 are listed in PostgreSQL 12.17 Release Notes. Other major changes and enhancements are as follows:
Added new configuration parameters pgpro_build, pgpro_edition, and pgpro_version, which report the Postgres 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.
Upgraded oracle_fdw to version 2.6.0.
Upgraded orafce to version 4.6.1.
Upgraded pg_filedump to version 16.0.
Upgraded pgbouncer to version 1.20.1.
Upgraded pg_probackup to version 2.6.6, which in particular improved stability of the
catchupcommand.Upgraded pgpro_controldata to version 16.1.0.
Upgraded pgpro_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 the pgpro_pwr report.Upgraded PTRACK to version 2.5.1 Enterprise.
E.3.2. Migration to Version 12.17.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.
While functions numeric_eq, numeric_ne, numeric_gt, numeric_ge, numeric_lt, and numeric_le are actually leakproof, they were not marked as such in Postgres 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 update pg_proc entries for these functions. You can run pg_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 the ALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq LEAKPROOF
When upgrading from Postgres 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 from Postgres Pro versions 12.6.2 or lower and take PTRACK backups using pg_probackup, retake a full backup after upgrade.