E.14. Postgres Pro Enterprise 14.2.1
Release Date: 2022-05-13
E.14.1. Overview
This release is based on PostgreSQL 14.2 and includes all the new features introduced in PostgreSQL 14, as well as bug fixes implemented in PostgreSQL 14.1 and 14.2 updates. For the detailed description, see PostgreSQL 14, PostgreSQL 14.1 and PostgreSQL 14.2 Release Notes, respectively.
For the list of extension modules and utilities specific to Postgres Pro Enterprise, as well as the main user-visible core changes over vanilla PostgreSQL, see Section 2. As compared to Postgres Pro Enterprise 13.6.1, the following differences are worth mentioning:
Implemented event triggers, which fire when an authenticated user logs in. For example, this feature can be used for verifying the connection and assigning roles according to circumstances, or for session data initialization.
Inherited the vanilla implementation of periodic verification of client-server connection during query execution. The corresponding
client_connection_check_intervalparameter is effectively disabled by default now.Fixed a security bug (CVE-2022-1552).
Removed the infrastructure for minor version upgrades without a server restart as a different approach to this feature is to be considered in the foreseeable future.
Implemented the evaluation-only version of the multimaster extension for now.
Implemented collecting statistics about vacuuming tables and indexes. The collected information is displayed in pgpro_stats views.
Upgraded pgpro_pwr to version 3.8, which particularly adds statistics on invalidation messages and on vacuuming tables and indexes to the report.
E.14.2. Migration to Version 14
You can migrate to Postgres Pro Enterprise 14 from the same or a previous version of PostgreSQL (that is supported by the upgrade method chosen) or Postgres Pro Standard/Postgres Pro Standard Certified and from a previous version of Postgres Pro Enterprise/Postgres Pro Enterprise Certified. The same holds for migration to Postgres Pro Enterprise Certified 14. See Section 18.6 for the methods to upgrade your database cluster. Consult the Postgres Pro Enterprise support team if you experience issues during migration. Backward migration is not supported. Note that migration from Postgres Pro Enterprise to Postgres Pro Enterprise Certified of the same major version (or vice versa) is an update between Postgres Pro compatible versions (see Section 18.6 for more details).
To migrate from PostgreSQL, Postgres Pro Standard, or Postgres Pro Enterprise 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.
When migrating from PostgreSQL or Postgres Pro Standard, make sure to pay special attention to implementation specifics of 64-bit transaction IDs. If you have used explicit casts to 32-bit integers when handling transaction IDs, you have to replace them with casts to bigint since 64-bit transaction IDs are of the bigint type.
Note
To avoid conflicts on Linux systems, do not use the postgrespro-ent-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 and installation instructions, see Chapter 17.
For other upgrade requirements imposed by vanilla PostgreSQL, see Section E.26.