E.1. Release Notes for Tantor SE-1C 16.10.2

E.1. Release Notes for Tantor SE-1C 16.10.2
Prev	Up	Appendix E. Release Notes	Home	Next

---

E.1. Release Notes for Tantor SE-1C 16.10.2 #

E.1.1. Review

E.1.2. Changes

E.1.3. Migration to version 16.10.2

Release date: 2025-10-09

E.1.1. Review #

Tantor SE-1C is a Russian-made DBMS based on the updated and improved version of the PostgreSQL DBMS. Tantor SE-1C 16.10.2 is based on PostgreSQL 16.

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

E.1.2. Changes #

Packaging and installation changes:

• Revised shared library lookup: the DBMS no longer relies on /etc/ld.so.conf.d entries for /opt/Postgresql/db/16/lib. Shared objects are resolved via embedded RPATH/RUNPATH in PostgreSQL binaries.

• Upgrade compatibility: postinst now invokes ldconfig -n /opt/Postgresql/db/16/lib/ to refresh the dynamic linker cache for the DBMS library directory only, ensuring correct resolution on systems that previously used ld.so.conf.d.

• Rationale (ALT Linux): addresses an issue where, after apt-get dist-upgrade and initramfs rebuild, paths from ld.so.conf.d were not included in the initramfs image. As a result, udevd in initramfs could not load libzstd.so, causing the boot process to stop at the initramfs stage.

• User impact: no actions required; the change is transparent during installation and upgrade.

E.1.3. Migration to version 16.10.2 #

When upgrading within the current major version and edition, install Tantor SE-1C 16.10.2 and restart the database server with command:

systemctl restart tantor-se-1c-server-16

To migrate from PostgreSQL or Tantor DB, first install the latest minor version and then perform a data dump/restore using pg_dumpall, or use the pg_upgrade utility.

Additionally, to migrate from a PostgreSQL database with the Citus Columnar extension to a PostgreSQL database with the Hydra Columnar extension, you can use the columnar_migrator script, which ensures data integrity and compatibility.

Tantor DB version 16 uses new naming conventions for SLRU cache size parameters. To migrate from version 15 to version 16 with respect to SLRU cache size parameters, use the script upgrade-SLRU-from-TT_15-to-TT_16-version.sh. The script is installed in /opt/tantor/db/16/tools/slru_upgrader/. For script usage, please define the PGDATA variable, which should specify the path to the cluster data directory of the migration target version (16). Help information is also available with the command /opt/tantor/db/16/tools/slru_upgrader/upgrade-SLRU-from-TT_15-to-TT_16-version.sh --help. The following table summarizes the changes in parameter names from Tantor DB 15 to Tantor DB 16:

Table E.1. Parameter Name Changes

Tantor DB 15	Tantor DB 16	Status
commit_ts_buffers	commit_timestamp_buffers	changed
serial_buffers	serializable_buffers	changed
subtrans_buffers	subtransaction_buffers	changed
xact_buffers	transaction_buffers	changed
multixact_members_buffers	multixact_member_buffers	unchanged
multixact_offsets_buffers	multixact_offset_buffers	unchanged
notify_buffers	notify_buffers	unchanged

---

Prev	Up	Next
Appendix E. Release Notes	Home	E.2. Release Notes for Tantor SE-1C 16.10.1