E.19. Postgres Pro Standard 12.5.1
Release Date: 2020-11-30
E.19.1. Overview
This release is based on PostgreSQL 12.5 and Postgres Pro Standard 12.4.1. All improvements inherited from PostgreSQL 12.5 are listed in PostgreSQL 12.5 Release Notes. Other major changes and enhancements are as follows:
Fixed a bug that caused
REINDEX CONCURRENTLYto leave incorrect indexes linked to orphaned types, which later resulted in "cache lookup failed for type xxx" errors duringVACUUM ANALYZE. If you used a concurrent reindex before and encounter these errors, to fix them, you can dump/restore the data, recreate the indexes, or contact our support team.Added pgpro_stats to Postgres Pro Standard. This extension combines tracking execution statistics of SQL statements and calculating wait event statistics.
Fixed a bug in the function for estimating the selectivity by index when evaluating a condition. Previously, the server could crash while executing this function if the type cache invalidation occurred at an unsuitable moment.
Ended support for Ubuntu 19.10 and added support for Ubuntu 20.10.
Ended support for Red Hat Enterprise Linux (RHEL) 6 and its derivatives: Oracle Linux 6 and CentOS 6.
Added support for OSnova 2.0. This is the first release to support this OS family.
Fixed a bug in the pg_variables module. Now you can create a variable in a transaction after removal of a variable with the same name.
Upgraded mamonsu to version 2.6.1.
Upgraded pgbouncer to version 1.15.
E.19.2. Migration to Version 12.5.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