E.2. Postgres Pro Standard 15.0.1

Release Date: 2022-11-10

E.2.1. Overview

This release is based on PostgreSQL 15 and includes all the new features introduced in PostgreSQL 15. For their detailed description, see PostgreSQL 15 Release Notes. Other major changes and enhancements are as follows:

  • Adapted the vanilla implementation of ICU collation support. The icu collation provider is still used by default for all locales, except C and POSIX. The syntax for specifying the provider of the default collation after the @ symbol is deprecated now.

  • Added a pilot implementation of SQL/JSON standard, including JSON constructor and SQL/JSON query functions, IS JSON predicates, and JSON_TABLE function. (See Section 9.16.3.)

  • Added support for Elbrus CPU architecture through ALT 9/10 for e2kv3/e2kv4, ALT 8.2 SP for e2kv3/e2kv4 and Astra Linux Leningrad 8.1 operating systems. You are recommended to use the 5.4.182-mcst-e8c-alt3.22.1 Linux kernel or newer when running ALT 10 for e2kv3/e2kv4.

  • Ended support for Windows operating systems.

  • Added tds_fdw extension that provides a foreign data wrapper to connect to Microsoft SQL Server and other databases that use the Tabular Data Stream (TDS) protocol.

  • Added rum module, which provides RUM index based on GIN, to Postgres Pro Standard.

  • Added pg_wait_sampling extension for sampling-based statistics of wait events to Postgres Pro Standard. With this extension, you can get an insight into the server activity, including the current wait events for all processes and background workers.

  • Achieved compatibility with TimescaleDB, which is an open-source database designed to make SQL scalable for time-series data.

  • Upgraded mamonsu to version 3.5.2, which provides new features and bugfixes. Notable changes are as follows:

    • Added autovacuum utilization metrics.

    • Added Zabbix macros based on plugin parameters from the configuration file, so that triggers can now be dynamically changed directly in Zabbix without updating the configuration file and restarting mamonsu.

  • Upgraded pg_probackup to version 2.5.9, which provides optimizations and bugfixes. Notable changes are as follows:

    • Fixed an issue with checkdb --amcheck, which previously completed with an error when the checked database contained partitioned indexes.

    • Fixed a backup failure on a replica that occurred because the version of the pg_probackup agent running there was different from that on the master.

  • Upgraded pgpro_pwr to version 4.1, which mainly adds JIT-related statistics to report tables.

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.2.2. Migration to Version 15

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. 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 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, do not use the postgrespro-std-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, see Chapter 16.

For upgrade requirements imposed by vanilla PostgreSQL, see Section E.4.