EuroDB 14.1 now delivers the newest, Enterprise-grade database solutions. The new version brings us fixes and updates for several tools that come with it, making them way more capable.
EuroDB is an Enterprise-grade database solution, which has the foolproof PostgreSQL engine at its heart. A variety of integrated modular tools wrap Postgres and extend its capabilities. Furthermore, the modules enhance the efficacy of management, allow for a broad analysis and security monitoring. In this article we’ll describe the most important changes in the tools EuroDB 14.1 provides, comparing them to their previous version.
It’s worthy to start the review of EuroDB’s updates and fixes with its most important aspect, that is the PostgreSQL database engine, which has been updated to version 14.1. The authors of the new version have noticeably taken care of the database performance, a new replication method and a emergency mode for a garbage collector. What’s more, version 13.3 and 14.0’s bugs have been fixed, resulting in an improved reliability also within edge cases, that are witnessed rarely. A comprehensive list of changes in PostgreSQL 14 is available in the article Underneath PostgreSQL 14 of ours.
Module: Log analysis
Apart from the updated Postgres version, the newest EuroDB version has been created with an updated log analysis module. Apart from bugfixes, the following changes can be seen in the changelog:
- the addition of new launcher options:
◦ --no-progressbar – hides the progress bar
◦ --day-report – allows to rebuild and HTML report for a specific day
◦ --keep-comments – allow to keep comments for normalized queries. Helpful for distinguishing queries
◦ --dump-all-queries – dumps all queries to a text file
◦ -Q | --query-numbering – numbers queries when --dump-all-queries or --normalized-only is used
◦ --tempdir – sets a directory for temporary files
◦ --ssh-port – sets SSH port. 22 is the default one
- the addition of incremental mode to the --iso-week-number option
- detection of QueryId in log_line_prefix
- PostgresPro logs compatibility
- SQL syntax decorator updated to the newest version
- detection of application names for authorized connections
- detection and ignoring of timestamps when creating graphs
- support for logs in the format that Google Cloud Platform or AWS use, as well as that pgbouncer version 1.11 uses
- creation of reports on session idle time
- addition of complete information on executed autovacuum processes
- support for new compression formats: zstd and lz4.
Module: Backup and restore
The backup module has been updated as well. This is a crucial functionality that critical systems of any enterprise are entrusted to operate. That’s why the freshest standards, that the newest version of the module delivers, are required. As part of the update, several bugs have been fixed and the following functionality has been included:
- the addition of new commands:
◦ verify-backup – check if a backup is made properly
◦ generate-manifest – generate the backup_manifest file from a provided backup_id
- the development of support for cloud technologies
◦ the ability to connect to Google Cloud Storage
◦ the providing of authentication via an SAS token (Azure blob storage) and Azure Managed Identity (the --credential option)
◦ the possibility to tag backup files and WAL archive on AWS or Azure (cloud storage)
◦ the addition of a compression algorithm (the python-snappy package must be installed)
- the addition of the new options: last_backup_minimum_size and last_wal_maximum_age to define server configuration parameters in a more precise way
- the change of a diagnosis date format to ISO 8601
- the addition of WAL files identification to avoid their double compression
- the form change from singular to plural of the commands: list-backup, list-server i show-server. From now on they will be named: list-backups, list-servers i show-servers. The singular forms will be preserved for backward compatibility.
- the inclusion of the “last-failed” shortcut to specify the last backup that failed
- the process of restoration of a very large number of files from an empty directory has its performance increased significantly.
The last module that has two freshly updated packages is the module for monitoring and managing logical replication. The module’s purpose is to keep up with the changes made to the main database and to replicate them to a backup database. This update provides an enhanced stability of this process and adds new functionality, the most important of which are:
- the creation of a rule so a note marked as „inactive” attempts to change its status to „active”. It can be disabled by setting the repmgrd_exit_on_inactive_node parameter as “true”
- the addition of the --repmgrd parameter to check the status of the manager that monitors a node
- the pglogical_show_subscription_table method fix to return a single row
- the assurance that the debug_query_string parameter is always set
bugfixes related to multi-insert
the fix related to double closing of relation when a BEFORE ROW DELETE trigger returns NULL
error status fix once a remote replication slot was incorrectly deleted.
The latest EuroDB 14.1 includes key updates to the most critical modules for the correct database operation. The base, that is PostgreSQL, has been upgraded to version 14.1. The upgraded modules for log analysis, backup, or the replication module all follow the constantly evolving standards of stability and security.