E.16. Postgres Pro Standard 15.0.1
Release Date: 2022-11-10
E.16.1. Overview
This release is based onPostgreSQL 15 and includes all the new features introduced in PostgreSQL 15. For their detailed description, seePostgreSQL 15 Release Notes. Other major changes and enhancements are as follows:
Adapted the vanilla implementation ofICU collation support. The
icucollation provider is still used by default for all locales, exceptCandPOSIX. 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 JSONpredicates, andJSON_TABLEfunction. (SeeSection 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.
Addedtds_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.
Addedrum module, which provides RUM index based on GIN, to Postgres Pro Standard.
Addedpg_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 withTimescaleDB, which is an open-source database designed to make SQL scalable for time-series data.
Upgradedmamonsu to version 3.5.2, which provides new features and bugfixes. Notable changes are as follows:
Added autovacuum utilization metrics.
AddedZabbix macros based on plugin parameters from the configuration file, so that triggers can now be dynamically changed directly inZabbix without updating the configuration file and restartingmamonsu.
Upgradedpg_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 thepg_probackup agent running there was different from that on the primary.
Upgradedpgpro_pwr to version 4.1, which mainly adds JIT-related statistics to report tables.
For the list of extension modules and utilities specific toPostgres Pro Standard, as well as the main user-visible core changes as compared to vanillaPostgreSQL, seeSection 2.
E.16.2. Migration to Version 15
You can migrate toPostgres Pro Standard 15 from the same or a previous version ofPostgreSQL (that is supported by the upgrade method chosen) and from a previous version ofPostgres Pro Standard orPostgres Pro Standard Certified. The same holds for migration toPostgres Pro Standard Certified 15. SeeSection 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 fromPostgres Pro Standard toPostgres Pro Standard Certified of the same major version (or vice versa) is an update betweenPostgres Pro compatible versions (seeSection 17.6 for more details).
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, make sure to install its latest available minor version and then perform a dump/restore usingpg_dumpall or use thepg_upgrade utility.
If you choose to runpg_upgrade, make sure to initialize the new database cluster with compatible parameters. In particular, pay attention to the provider of the default collation and thechecksum settings in the cluster you are migrating from. To find out the default collation and its provider in the original cluster, see thedatcollate value for thetemplate0 database in thepg_database catalog. If you are upgrading from a version where provider of the default collation is not specified, uselibc provider if upgrading from vanillaPostgreSQL, and omit the provider if upgrading from earlier versions ofPostgres Pro. If you are upgrading yourPostgres Pro installation from version 9.6 or lower, and you want to keep the existing ICU collation, set--icu-locale to thelc_collate value of your old cluster. Ifpg_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 usepg_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 thepostgrespro-std-15 package to install the newPostgres 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, seeChapter 16.
For upgrade requirements imposed by vanillaPostgreSQL, seeSection E.30.