E.4. Postgres Pro Standard 17.0.1#
Release Date: 2024-11-02
E.4.1. Overview#
This release is based onPostgreSQL 17 and includes all the new features introduced in PostgreSQL 17. For their detailed description, seePostgreSQL 17 Release Notes. Other major changes and enhancements are as follows:
Added the
SPLIT PARTITIONandMERGE PARTITIONSsubcommands to theALTER TABLEcommand. The subcommands split a single partition into several partitions and merge several partitions into one, respectively, hence improving partitioned table management.Removed the ability to create constructs using
JSON_EXISTS()with theRETURNINGclause, which in earlier versions allowed the function to return values of any type. This syntax is not supported by the SQL/JSON standard, which states that theJSON_EXISTS()predicate should only return TRUE, FALSE, or UNKNOWN.Added thepgpro_autopart extension that allows dynamic partition creation by using triggers on the partitioned table view.
Upgraded the ODBC driver to version 17.00.0002.
Upgradedaqo to version 3.0, which provides the following major changes and enhancements:
Introduced the sandbox mode, which allows working in an isolated environment without touching the mainaqo knowledge base. This mode can be turned on either on a primary or a standby node by settingaqo.sandbox to on.
Introduced a learning mechanism whereaqo adjusts the planner's row count estimates with its own predictions. It can be turned on by enablingaqo.delta_rows.
Upgradedoracle_fdw to version 2.7.0.
Upgradedorafce to version 4.13.5.
Upgradedpgpro_controldata to version 17.1.0.
Upgradedpg_filedump to version 17.1.
Upgradedpg_probackup to version 2.8.4.
Upgradedpgpro_pwr to version 4.7, which provides new features and optimizations. Notable changes are as follows:
Asubsample feature to collect relatively fast changing data.
New report tables, specifically regarding session states.
Support for newPostgres Pro 17 statistics.
A possibility not to reset statistics of the statistics collecting extension during taking a sample.
Upgradedpgpro_stats to version 1.8, which supportsPostgres Pro 17. Notable changes are as follows:
Updated
pgpro_stats_statementsandpgpro_stats_totalsviews to include fields added topg_stat_statements. Related functions were updated accordingly.Streamlined access to views and functions. Specifically, access to the
pgpro_stats_archiver,pgpro_stats_vacuum_database,pgpro_stats_vacuum_tables, andpgpro_stats_vacuum_indexesviews was granted to all users. Previously, these views required explicitly granting access rights. Access to execution of thepgpro_stats_trace_resetfunction, which could previously be executed by any user, was restricted to superusers.
Upgradedpg_repack to version 1.5.1.
Upgradedpg_wait_sampling to provide tracking of subquery IDs and utility statements and to add the new
pg_wait_sampling.sample_cpuparameter, which allows specifying the sampling mode that determines whether to perform sampling of on-CPU backends.Upgraded the PLV8 extension to version 3.2.3.
Upgradedtds_fdw to version 2.0.4.
Deprecated the
pgpro_version,pgpro_edition, andpgpro_buildfunctions, which will be removed in future releases. Use thepgpro_version,pgpro_edition, andpgpro_build configuration parameters instead.Removed the deprecatedpg_pathman extension.
Ended support for AlterOS 7, ALT 8.2 SP, ALT 9, Debian 10, SLES 12, Ubuntu 23.10.
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.4.2. Migration to Version 17#
You can migrate toPostgres Pro Standard 17 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 17. 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 are migrating fromPostgres Pro Standard version 16 or 15, and your database contains objects using the invalid syntax ofJSON_EXISTS() with theRETURNING, delete or replace them with valid alternatives before upgrading.
If you choose to runpg_upgrade, make sure to initialize the new database cluster with compatible parameters. In particular, pay attention to thechecksum settings in the cluster you are migrating from. 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-17 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.10.