This release is based on PostgreSQL 12.9 and Postgres Pro Standard 12.8.1. All improvements inherited from PostgreSQL 12.9 are listed in PostgreSQL 12.9 Release Notes. Other major changes and enhancements are as follows:
Dropped support for the sr_plan extension.
Upgraded mamonsu 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 the mamonsu configuration file.
A critical issue is fixed that could arise when the
bootstrapstep was skipped. In this case, although a user can work with mamonsu under superuser permissions, the special
mamonsuschema is not created, but after creating the auxiliary extension pg_buffercache in any other schema, running mamonsu 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 a pg_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.
Fixed pg_dumpall to avoid using an insecure search path.
Upgraded pgpro_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 in Postgres Pro 14.
Migration to Version 12.9.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.
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.