Tsurugi 1.1.0 - Release Notes (en)

[akirakw]

1.1.0 Release Notes

Overview

In this version, several improvements to the job scheduler of the SQL execution engine have enhanced performance, especially when executing a large number of queries simultaneously. Additionally, optimizations during database startup have significantly reduced the startup time after transaction log compaction.

Furthermore, this version includes several important bug fixes. We strongly recommend that all users of the previous version upgrade to this version.

New Features and Improvements

• SQL

  • Improved parallel execution of SQL jobs by dividing control of scan a wide range of records in the job scheduler
    • Resolved the following Known Issues: TSURUGI-IS-706
  • Improved parallel execution of SQL jobs by optimizing scheduling for non-sticky tasks in the job scheduler
  • Improved performance degradation caused by improper waiting for transaction log writes when sql.commit_response=AVAILABLE is set

• Transaction

  • Significantly reduced database startup time after transaction log compaction
    • For details on the improvement, see the following Known Issues: TSURUGI-IS-289

Bug Fixes

• SQL

  • TSURUGI-IS-957 The results of the MIN and MAX functions on CHAR type may be incorrect.
  • Fixed an issue where queries with JOIN clauses involving many tables could adopt a full scan instead of being properly optimized
  • Fixed an issue where queries combining OR and IS NULL might not work correctly

• Transaction

  • Fixed data could be lost in very rare cases if the database was improperly shut down when sql.commit_response=STORED was specified
    • For potential performance degradation in some cases due to this fix, see the following Known Issues: TSURUGI-IS-944
  • Fixed an issue on Ubuntu 24.04 where specifying a path ending with / as the argument for tglogutil compaction could result in a No such file or directory error and the specified directory disappearing
  • Fixed an issue where starting a new RTX transaction after data was updated during an existing RTX transaction could cause the new transaction to read the same snapshot as the previous one
  • Fixed an issue where transaction consistency violations might not be detected when multiple transactions using INSERT OR REPLACE were processed within the same epoch

• Endpoint

  • The database may become unstable if the ResultSet is closed without reading to the end
    • This issue can occur when using Tsubakuro or Iceaxe if the ResultSet is closed without reading to the end, and also when retrieving records that exceed the client variable setting select.maxlines (default: 1000) in tgsql.

Known Issues

For known issues in this version and supplementary information on issues fixed in this version, refer to the following link:

• Tsurugi 1.1.0 - Known Issues(ja)

Others

For a list of changes in this version, refer to the following Changelog:

• Tsurugi 1.1.0 - Changelog

For upgrade instructions from previous versions, refer to the following document:

• Tsurugi Upgrade Guide

---

This discussion was created from the release 1.1.0.