3. What are the differences between Tantor SE 1C 16 and PostgreSQL 16#
3. What are the differences between Tantor SE 1C 16 and PostgreSQL 16 #
- 3.1. Helpful links
- 3.2. Core improvements
- 3.3. Additional Supplied Utilities
- 3.4. Additional Supplied Utilities
- 3.5. Tantor Additional Programs Distributed as Separate Packages
- 3.6. Additional External Modules Distributed as Separate Packages
- 3.7. Programmatic Interfaces for Various Languages
- 3.8. Release Notes
- 3.9. How to configure Tantor SE-1C parameters for 1C
3.1. Helpful links #
3.2. Core improvements #
64-bit transaction counter.
Logical replication between DBMS clusters using 32-bit and 64-bit transaction identifiers.
Improved performance with a large number of simultaneous users due to improvements in the SLRU mechanism, which was made in PostgreSQL 17.
Increased number of partitions in the shared buffers.
Optimized
pglzdata compression algorithm (~1.4 times).Reduced the number of data page locks in the shared buffers.
libpq compression.
Optimization and acceleration of the cascade replication recovery process (standby fadvise).
Ability to end a transaction based on a preset timeout.
Support for extensions and data types for compatibility with 1C.
Detailed computation of planner cost estimates for sort operations using the enable_detailed_sort_cost setting.
SIMD enhancements for x86 (SSE2) and ARM (NEON) architectures have been introduced, leading to improvements in transaction processing. These advancements also contribute to faster operations with jsontext, thereby boosting overall data stream processing efficiency.
Optimization for linear search for ARM64 architecture processors.
When sending the WAL to the standby server, a checksum of the data blocks is verified.
Increased informative value of diagnostic information:
Diagnostics of internal DBMS errors (
backtrace_on_internal_errorparameter).The informativeness of the DBMS server logs — the start messages contain additional diagnostic information.
The pg_controldata server application contains additional meta information about the edition and assembly to simplify the diagnosis of possible problems.
The maximum size of data in table cells supported by the pg_dump module is 2 GB.
3.3. Additional Supplied Utilities #
pgcompacttable — a tool designed to reduce the size of bloated tables and indexes without using heavy locks. It is developed to reorganize data in tables and rebuild indexes in order to reclaim disk space without impacting database performance.
pgcopydb — a tool that automates running pg_dump | pg_restore between two running Postgres servers. To make a copy of a database to another server as quickly as possible, one would like to use the parallel options of pg_dump and still be able to stream the data to as many pg_restore jobs.
3.4. Additional Supplied Utilities #
data_generator — generates fake data for testing and development purposes. It supports various data types and allows customization of generated data through templates.
pgcompacttable — reduces the size of bloated tables and indexes without using heavy locks. It is developed to reorganize data in tables and rebuild indexes in order to reclaim disk space without impacting database performance.
pgcopydb — automates running pg_dump | pg_restore between two running Postgres servers. To make a copy of a database to another server as quickly as possible, one would like to use the parallel options of pg_dump and still be able to stream the data to as many pg_restore jobs.
slru_upgrader — automatically renames the configuration parameters related to the SLRU buffers during a major version upgrade from Tantor SE-1C 15. This utility helps to avoid the issue of the server failing to start after the upgrade due to the presence of old parameter names in the
postgresql.conffile.
3.5. Tantor Additional Programs Distributed as Separate Packages #
Tantor Platform — full-featured modular platform for administration and monitoring of Tantor RDMS and most PostgreSQL based clusters. The platform simplifies daily RDBMS operation with significant impact on the RDBMS management simplicity. The software functionality includes: smart and simple user interface, cluster automatic adaptive tuning, system overview, alerts and monitoring, automatic health checks and schema audit, maintenance tasks resolution through the GUI, advanced query profiling, and administering multiple servers in one place.
pg_anon — a standalone Python program to work with Tantor RDMS or PostgreSQL based DB to perform data masking and anonymization during data migration between production and test environments.
pg_cluster — an ansible playbook for PostgreSQL high availability cluster on Patroni.
pg_configurator — a PostgreSQL configuration tool.
3.6. Additional External Modules Distributed as Separate Packages #
ldap2pg — a tool that automates the synchronization of PostgreSQL roles and their privileges from an LDAP directory (or a YAML config), creating, updating, and dropping roles to match your enterprise directory.
mysql_fdw — a PostgreSQL Foreign Data Wrapper that lets Postgres query and manipulate tables on a remote MySQL server as if they were local, supporting SELECT/INSERT/UPDATE/DELETE and push-down optimizations.
pg_timetable — an advanced, standalone PostgreSQL job scheduler that runs SQL, system programs, and built-in tasks on custom cron or interval schedules with support for chained workflows and database-driven configuration.
pgbouncer — a lightweight PostgreSQL connection pooler that sits between clients and the database to manage and reuse backend connections efficiently, reducing overhead and improving concurrency for high-load workloads.
tds_fdw — a PostgreSQL Foreign Data Wrapper that lets PostgreSQL connect to and query databases using the Tabular Data Stream (TDS) protocol, such as Microsoft SQL Server and Sybase, exposing their tables as foreign tables.
wal-g — a tool for making encrypted, compressed Tantor SE-1C backups (full and incremental) and push/fetch them to/from storage without saving it on your filesystem.
3.7. Programmatic Interfaces for Various Languages #
Tantor SE-1C provides a wide range of drivers and libraries to interact with the database from various programming languages and environments. The following sections outline the main interfaces and their respective tools.
3.7.1. C/C++ #
libpq: The primary C library for Tantor SE-1C client programs. It allows sending queries, receiving results, and managing connections.
libpqxx: A C++ wrapper over libpq, offering a more modern and user-friendly interface for C++ developers.
3.7.2. Java/JDBC #
PostgreSQL JDBC Driver: The official JDBC driver that enables Java applications to interact with Tantor SE-1C databases using the standard JDBC API.
3.7.3. .NET #
Npgsql: An open-source .NET Data Provider for PostgreSQL. It allows .NET applications to use ADO.NET to connect to Tantor SE-1C, run queries, and retrieve data.
3.7.4. ODBC #
psqlODBC: The official PostgreSQL ODBC driver providing connectivity for applications and tools using ODBC interfaces.
3.7.5. Perl #
DBD::Pg: A Perl DBI-compliant module for Tantor SE-1C. It integrates seamlessly with the Perl DBI framework for database interactions.
3.7.6. Python #
psycopg2/psycopg: Widely used Python adapters implementing the Python DB-API specification. They provide a robust and efficient way to execute queries, handle transactions, and manage connections.
pg8000: A pure-Python alternative adapter that also supports the DB-API standard.
3.7.7. Ruby #
pg gem: The official Ruby driver for PostgreSQL, providing a native interface to execute queries and process results.
3.7.8. Tcl #
pgtcl/pgtcl-ng: Tcl extensions enabling connections to Tantor SE-1C, execution of queries, and management of query results within Tcl scripts.
3.8. Release Notes #
The first release of Tantor SE-1C is 16.2.1.
Significant changes can be found on the related page.
All other changes see in Release Notes.