E.20. Postgres Pro Standard 14.1.1
Release Date: 2021-12-01
E.20.1. Overview
This release is based on PostgreSQL 14.1 and includes all the new features introduced in PostgreSQL 14, as well as bug fixes implemented in PostgreSQL 14.1. For their detailed description, see PostgreSQL 14 Release Notes and PostgreSQL 14.1 Release Notes, respectively. Other major changes and enhancements are as follows:
Removed the sr_plan extension.
Added several enhanced security mechanisms to Postgres Pro Standard:
pg_proaudit extension that enables detailed logging of various security events.
Advanced authentication policies that provide effective password management and access control. (See CREATE PROFILE and ALTER ROLE).
Built-in integrity checks for executable files, configuration files, and system tables. (Certified edition only.)
Built-in data security mechanisms that enable sanitizing an object by filling it with zeroes before deletion. Zeroing can be done before purging files in external memory and removing outdated row versions (page vacuum), freeing RAM, and deleting or overwriting WAL files. (Certified edition only.)
Upgraded mamonsu to version 3.1.0, which supports Postgres Pro 14 and adds a new option for
bootstrap. With this option, ifdbnameis not explicitly specified, its value will be automatically set to the database name defined in the[postgres]section of the mamonsu configuration file.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.
Removed the
WAITLSNcommand.
For the list of extension modules and utilities specific to Postgres Pro Standard, as well as the main user-visible core changes as compared to vanilla PostgreSQL, see Section 2.
E.20.2. Migration to Version 14
You can migrate to Postgres Pro Standard 14 from the same or a previous version of PostgreSQL (that is supported by the upgrade method chosen) and from a previous version of Postgres Pro Standard or Postgres Pro Standard Certified. The same holds for migration to Postgres Pro Standard Certified 14. See Section 17.6 for the methods to upgrade your database cluster. Consult the Postgres Pro Standard support team if you experience issues during migration. Backward migration is not supported. Note that migration from Postgres Pro Standard to Postgres Pro Standard Certified of the same major version (or vice versa) is an update between Postgres Pro compatible versions (see Section 17.6 for more details).
To migrate from PostgreSQL or a Postgres Pro Standard release based on a previous PostgreSQL major version, make sure to install its latest available minor version and then perform a dump/restore using pg_dumpall or use the pg_upgrade utility:
If you choose to run pg_upgrade, make sure to initialize the new database cluster with compatible parameters. In particular, pay attention to the provider of the default collation and the checksum settings in the cluster you are migrating from. If pg_upgrade creates any SQL files in its current directory, run these files to complete the upgrade.
If you are opting for a dump/restore, do not forget to use the
--add-collprovideroption to correctly choose the provider for the default collation of the migrated database.
To find out the default collation and its provider in the original cluster, see the datcollate value for the template0 database in the pg_database catalog. If you are upgrading from a version where provider of the default collation is not specified, use libc provider if upgrading from vanilla PostgreSQL, and omit the provider if upgrading from earlier versions of Postgres Pro.
Besides, note the following collation-related upgrade specifics described below.
On Windows, Postgres Pro Standard installations could contain databases with default collations provided by ICU, where the name of the database default collation used a syntactically correct BCP 47 language tag format, but had a wrong language code or other parameters, which invalidated the database default collation name for ICU.
If this issue affects the template0 database, you will get the following error message when trying to initialize the cluster with the same collation: failed to get the canonical name for collation locale. In this case, you can only use dump/restore for upgrade, specifying a valid locale for the selected collation provider.
If this issue affects other databases, you will get the same error message when Postgres Pro tries to create these databases with invalid collation in the new cluster. In this case, you can try the following:
Make a dump of the database using pg_dump; it is required to use
--createand--format=plainoptions.Change the provider for the default collation of the database in the dump file from
'@icu'to'@libc'.In psql, restore the modified dump to complete the upgrade. This operation may fail if any constraints depending on the database collations are violated. In this case, you can try resolving the issues manually.
When upgrading the installation from version 10 or lower, a dump/restore is recommended. In this case, you may have to resolve constraint violations manually. If this option is infeasible, you can still use pg_upgrade, but consult the Postgres Pro Standard support team since the integrity of indexes and constraints might be violated in some cases.
Note
To avoid conflicts on Linux systems, do not use the postgrespro-std-14 package to install the new Postgres Pro binaries. Use the individual packages instead. In this case, server autostart needs to be enabled manually, if required. For details on the available packages, see Chapter 16.
For upgrade requirements imposed by vanilla PostgreSQL, see Section E.36.