E.18. Postgres Pro Standard 12.9.1
Release Date: 2021-11-25
E.18.1. Overview
This release is based onPostgreSQL 12.9 andPostgres Pro Standard 12.8.1. All improvements inherited fromPostgreSQL 12.9 are listed inPostgreSQL 12.9 Release Notes. Other major changes and enhancements are as follows:
Dropped support for thesr_plan extension.
Upgradedmamonsu to version 3.1.0. Notable changes are as follows:
A new option for
bootstrapis added. With this option, if-dbnameis not explicitly specified, its value will be automatically set to the database name defined in the[postgres]section of themamonsu configuration file.A critical issue is fixed that could arise when the
bootstrapstep was skipped. In this case, although a user can work withmamonsu under superuser permissions, the specialmamonsuschema is not created, but after creating the auxiliary extensionpg_buffercache in any other schema, runningmamonsu resulted in errors“ERROR: relation "mamonsu.pg_buffercache" does not exist...”.
Added support for ALT Linux 10.
Changed the minimum supported Windows versions to Windows 10 and Windows Server 2012 R2.
Ended support for Ubuntu 20.10 and added support for Ubuntu 21.10.
Fixed apg_probackup issue with archiving WAL from a directory outside of the data directory. Previously, multi-threaded and batch optimizations of
archive-pushprevented such archiving; now it is possible to archive WAL from any directory, but if it is outside of the data directory, multi-threaded and batch optimizations are automatically turned off.Fixedpg_dumpall to avoid using an insecure search path.
Upgradedpgpro_pwr. Major enhancements are as follows:
Added the“Load distribution” section to the report, which shows load distribution of different resources (for example, total time or shared blocks written) for heavily loaded objects, such as databases, applications, hosts, or users, in graphics, as stacked bar charts.
Added the“Session statistics by database” and“WAL statistics” report tables, based on new views and fields made available inPostgres Pro 14.
Deprecated
WAITLSNcommand.
E.18.2. Migration to Version 12.9.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.