E.1. Release Notes for Tantor SE 17.10.0#
E.1. Release Notes for Tantor SE 17.10.0 #
Release date: 2026-05-20
E.1.1. Review #
Tantor SE is a Russian-made DBMS based on the updated and improved version of the PostgreSQL DBMS. Tantor SE 17.10.0 is based on PostgreSQL 17 and includes all the new features introduced in PostgreSQL 17, as well as changes included in the PostgreSQL 17.10 and previous releases of Tantor SE.
The list of changes in Tantor SE 17.10.0 compared to the previous release is listed below.
E.1.2. DBMS Core Functionality #
The following changes have been made to improve the DBMS:
Fixed the suboptimal application of selection by the
EXISTS,INconstruction.Fixed the error of overestimating Hash Join estimates when using the
COALESCEfunction.Fixed a bug during the major upgrade of Tantor SE from version 16.13 to 17.9.
E.1.3. Fixes for Additional Supplied Modules #
Fixed the issue of concurrency when enabling the pg_store_plans extension.
Fixed the operation of the page_repair extension.
Tracking of
shared_preload_librarieshas been added to the transp_anon extension.
E.1.4. Fixes for Additional Supplied Utilities #
The pg_diag_setup utility has been refactored: the logic for determining paths to configuration files and data directory has been improved, which ensures the correct processing of PostgreSQL clusters running with a relative path to data directory.
E.1.5. Operating System Support #
Support for OS builds has been discontinued:
Astra Linux Special Edition 2.12
Centos 7
Debian 10 Buster
Ubuntu 18
Ubuntu 20
E.1.6. Migration to version 17.10.0 #
When upgrading within the current major version and edition, install Tantor SE 17.10.0 and restart the database server with command:
systemctl restart tantor-se-server-17
To migrate from PostgreSQL or Tantor DB, first install the latest minor version and then perform a data offload/restore by applying pg_dumpall, or use the pg_upgrade utility.
For correct execution of pg_upgrade, absolute paths to the binary directories and database cluster directories must be specified. Relative paths are not supported and may lead to errors.
Warning
When updating skipping previous major versions (for example, from version 15 to 17 at once), it is recommended to pre-execute VACUUM FREEZE for all cluster databases.
If VACUUM FREEZE is not possible, it is recommended to upgrade sequentially, installing each major version in order.