3. What are the differences between Tantor BE 16 and PostgreSQL 16#
3. What are the differences between Tantor BE 16 and PostgreSQL 16 #
3.1. Helpful links #
3.2. Core improvements #
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.
Optimized replication recovery process (
fadviseon standby).Ability to end a transaction based on a preset timeout.
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. Additionally supplied modules (extensions) #
page_repair - designed to repair separate corrupted pages using backup data from the replication server. It allows saving reparation time as it does not require reparation of all data, but separate pages.
pg_background - allows executing commands in the background mode such as VACUUM and CREATE INDEX CONCURRENTLY from SQL along with launching autonomous transactions.
pg_cron - represents a cron-based job scheduler working within the database as an extension. It uses the same syntax as regular cron, but it allows scheduling Tantor DBMS commands directly from the database.
pg_repack - removes bloat from tables and indexes, and optionally restores the physical order of clustered indexes. Unlike CLUSTER and VACUUM FULL it works online, without holding an exclusive lock on the processed tables during processing.
pg_store_plans - provides the means to keep track of the execution plan statistics for all SQL statements executed by the Tantor server.
pg_wait_sampling - provides information about current waiting event for a certain process. However, to collect a descriptive statistics of server behaviour a user must repeatedly collect the current waiting event. This module represents an extension for collecting sample statistics of waiting events that prevent needless sampling of the current event waiting.
pgaudit - provides detailed session and/or object audit logging via the standard Tantor DBMS logging facility. The goal of the pgAudit is to provide Tantor DBMS users with capability to produce audit logs often required to comply with government, financial, or ISO certifications.
pgauditlogtofile - is an addon to pgAudit than will redirect audit log lines to an independent file, instead of using PostgreSQL server logger. This will allow us to have an audit file that we can easily rotate without polluting server logs with those messages. Audit logs in heavily used systems can grow very fast. This extension allows to automatically rotate the files based in a number of minutes.
pgl_ddl_deploy - is an extension for sending DDL commands to a replica server during logical replication.
3.5. Additionally supplied programs #
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: is 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;
wal-g: is a tool for making encrypted, compressed Tantor BE backups (full and incremental) and push/fetch them to/from storage without saving it on your filesystem;
pg_configurator: is a PostgreSQL configuration tool;
pg_cluster: is a Ansible playbook for PostgreSQL high availability cluster on Patroni.
3.6. Release Notes #
The first release of Tantor BE is 16.2.1.
Significant changes can be found on the related page.
All other changes see in Release Notes.