E.15. Postgres Pro Enterprise 15.1.1
Release Date: 2023-02-01
E.15.1. Overview
This release is based on PostgreSQL 15.1 and includes all the new features introduced in PostgreSQL 15, as well as bug fixes implemented in PostgreSQL 15.1 update. For the detailed description, see PostgreSQL 15, and PostgreSQL 15.1 Release Notes.
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 14.6.1, the following differences are worth mentioning:
Implemented packages, which are essentially enhanced schemas that help to organize named objects with a related purpose. This feature provides extended functionality, familiar to Oracle users, for PL/pgSQL where new function modifiers and conventions were introduced, as well as new
CREATE PACKAGEandDROP PACKAGEcommands.Added support for passing named and positional arguments to scripts invoked by the
\icommand in psql.Released pg_probackup 2.6 Enterprise. This is the first version of pg_probackup enterprise edition, which provides the following features:
Optimized pg_probackup input/output engine to improve performance.
Added Simple Storage Service (S3) support for storing data in private clouds. S3 interface was tested with MinIO object storage and VK Cloud storage. Note that pg_probackup provides complete processing of S3 interface logging.
Added CFS (Compressed File System) support for incremental backups in
DELTA,PAGE, andPTRACKmodes.PTRACKmode requires PTRACK 2.4.0 or higher and is recommended as the fastest mode for incremental backups.Added support for lz4 and zstd compression algorithms.
Ended support for Postgres Pro 9.6.
Added the pgpro_anonymizer extension that provides the ability to mask or replace personally identifiable information or commercially sensitive data from a Postgres Pro database.
Inherited the vanilla implementation of pgbench improvement that allows to retry after serialization and deadlock failures.
Upgraded the PLV8 extension to version 3.1.5.
Implemented the evaluation-only version of the multimaster extension that cannot be used in production for now.
E.15.2. Migration to Version 15
You can migrate to Postgres Pro Enterprise 15 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 15. 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. 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. If you are upgrading your Postgres Pro installation from version 9.6 or lower, and you want to keep the existing ICU collation, set --icu-locale to the lc_collate value of your old cluster. If pg_upgrade creates any SQL files in its current directory, run these files to complete the upgrade.
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, do not use the postgrespro-ent-15 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.