E.1. Release Notes for Tantor SE 18.3.0#

E.1. Release Notes for Tantor SE 18.3.0
E.1. Release Notes for Tantor SE 18.3.0
Prev UpAppendix E. Release NotesHome Next

E.1. Release Notes for Tantor SE 18.3.0 #

E.1.1. Review
E.1.2. DBMS Core Functionality
E.1.3. Additional Supplied Modules
E.1.4. Installation and update changes
E.1.5. Operating System Support
E.1.6. Supported Operating Systems
E.1.7. Migration to version 18.3.0

Release date: 2026-06-15

E.1.1. Review #

Tantor SE is a Russian-made DBMS based on the updated and improved version of the PostgreSQL DBMS. Tantor SE 18.3.0 is based on PostgreSQL 18.

Below are the additional modules and utilities added to Tantor SE, as well as a list of changes to the server core.

E.1.2. DBMS Core Functionality #

The following changes have been made to improve the DBMS:

  • Implemented logical replication between DBMS clusters using 32-bit and 64-bit transaction identifiers.

  • Added the ability to work with temporary tables on a physical replica.

  • The tuples_fetched parameter has been added to the output of the EXPLAIN command, which allows you to evaluate the efficiency of using the index.

  • The output of the EXPLAIN command adds additional statistics on the usage of the Memoize node.

  • Added the ability to scan temporary tables in parallel using the extended_parallel_processing and write_page_cost parameters.

  • The verification of the IN operator condition when working with MCV histograms has been optimized.

  • Added the ability to use Commit Sequence Number (Commit Sequence Number, CSN is a monotonically increasing 64-bit number assigned to each transaction at the moment it commits) to optimize row visibility detection in transaction snapshots.

  • Added the ability to use Compression Storage Manager (CSM) with database pages at the storage manager level Tantor SE.

  • Added the ability to start WAL receiver earlier on the standby server using the wal_receiver_start_at parameter, which reduces unnecessary delays when resuming streaming replication after a replay backlog.

  • Added the ability to partially perform aggregation before joining tables, followed by finalizing after the connection is completed using the enable_eager_aggregate parameter. This allows you to reduce the amount of data processed and choose a more efficient execution plan.

  • Fixed a bug that causes local buffers to run out when working with temporary tables with high effective_io_concurrency values.

  • An optimization has been implemented that allows you to move semi-connections inside the query connection tree. This allows you to reduce the amount of data processed and choose a more efficient execution plan.

  • Implemented a check that warns about the simultaneous use of incompatible parameters extended_parallel_processing and enable_temp_memory_catalog.

  • The possibility of choosing a cardinality estimation model is implemented. There are 2 models available to choose from: Fully independent and Partially correlated.

  • Added support for CREATE TEMP TABLE ... ON COMMIT DROP for temporary tables when using stored in-memory temporary catalog.

Caution

The value of the jit parameter has been changed to off by default.

E.1.3. Additional Supplied Modules #

pgaudit:

  • Implemented monitoring of user activity outside the whitelist of whitelist_role with event logging.

  • For users from the whitelist_role whitelist, the option has been added not to audit operations in temporary schemas.

The transp_anon implements data anonymization has been implemented at the table access method level, which allows you to cover all possible workarounds. Improved performance.

Added extensions:

  • csn — provides functions for retrieving the Commit Sequence Number associated with transactions and snapshots.

  • pg_csm — provides a diagnostic estimation of compressibility of tables and indexes that use the Compression Storage Manager.

  • pg_ilm — data lifecycle management extension for Tantor SE intended to compute archiving recommendations for regular tables and leaf partitions.

Updated extensions:

Removed extensions:

The pg_uuidv7 extension has been removed from contrib for Tantor SE 18 and later, because UUIDv7 generation is now supported by PostgreSQL core. The UUIDv7 generation function remains available under the same name: 

uuidv7()

E.1.4. Installation and update changes #

Link-Time Optimization (LTO) is enabled for release builds.

E.1.5. Operating System Support #

Added build support for OS Altlinux p11 and Debian 13 Trixie.

Discontinued build support for OS Debian 10 Buster and Ubuntu 20.

E.1.6. Supported Operating Systems #

The list of supported operating systems (OS) has been expanded. The full list is provided below:

  • Altlinux c9f2 (P8)

  • Altlinux p10

  • Altlinux p11

  • Astra Linux Special Edition 1.7

  • Astra Linux Special Edition 1.8

  • Astra Linux Special Edition 4.7

  • Debian 11 Bullseye

  • Debian 12 Bookworm

  • Debian 13 Trixie

  • MSVSphere

  • Oracle Linux 8

  • Redos 7.3

  • Redos 8

  • Rocky 8

  • Rocky 9

  • Ubuntu 22

DBMS builds are created and tested for these operating systems on an ongoing basis.

Other x86-64 architecture operating systems are supported on request.

E.1.7. Migration to version 18.3.0 #

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.

Caution

Starting with PostgreSQL 18, clusters initialized with initdb have data page checksums enabled by default. This may affect upgrades from clusters created without checksums: pg_upgrade requires the old and new clusters to use the same checksum setting. If you upgrade to version 18.3.0 using pg_upgrade from a non-checksum-enabled cluster, initialize the new cluster with initdb --no-data-checksums, or enable checksums in the old cluster before running pg_upgrade.

Prev Up Next
Appendix E. Release Notes Home E.2. Release 18.3