Tsurugi 1.5.0 - Release Notes (en)

[akirakw]

Tsurugi 1.5.0 Release Notes

Overview

Tsurugi 1.5.0 introduces several enhancements to SQL features, including support for the LIKE operator, new built-in functions, and improved compatibility. For transactions, RTX parallel scan—officially supported since the previous version—now allows clients to specify the number of parallel tasks per transaction.

This release also includes important bug fixes and stability improvements. We strongly recommend all users of previous versions to upgrade to this release.

New Features and Improvements

SQL

• Added support for the LIKE operator
  • The LIKE operator enables pattern matching on strings using the % and _ wildcards for partial matches.
  • Example: SELECT * FROM t WHERE c LIKE 'pattern%'
  • For more details, see:
    • https://github.com/project-tsurugi/jogasaki/blob/master/docs/like-ja.md
• Added support for the ROUND function
  • The ROUND function rounds numbers to the specified number of decimal places.
  • Example: SELECT ROUND(c, 2) FROM table
  • For more details, see:
    • https://github.com/project-tsurugi/jogasaki/blob/master/docs/round-ja.md
• Added support for ENCODE and DECODE functions
  • The ENCODE function converts binary data to a Base64-encoded string. For details, see:
    • https://github.com/project-tsurugi/jogasaki/blob/master/docs/encode-ja.md
  • The DECODE function converts a Base64-encoded string to binary data. For details, see:
    • https://github.com/project-tsurugi/jogasaki/blob/master/docs/decode-ja.md
• Added support for implicit conversion from string literals to date/time data types in INSERT/UPDATE statements
  • Example: INSERT INTO table (date_col) VALUES ('2023-10-01')
  • For details on implicit conversions, see:
    • https://github.com/project-tsurugi/tsurugidb/blob/master/docs/sql-features.md#conversions
• Added support for positional placeholders (?)
  • In addition to the traditional :variable placeholders, you can now use ? placeholders to assign values in queries.
  • Example: SELECT * FROM table WHERE c1 = ? AND c2 = ?
  • For more details, see:
    • https://github.com/project-tsurugi/tsurugidb/blob/master/docs/sql-features.md#placeholders

Transaction

• Added support for specifying the number of parallel tasks per transaction when using RTX parallel scan
  • You can now specify the number of parallel tasks as a transaction option when starting an RTX transaction from client APIs or tgsql.
    • Example: In tgsql, use BEGIN READ ONLY WITH PARALLEL=8; to set the number of parallel tasks to 8 for the transaction.
  • This allows, for example, faster scans in transactions that may involve large data scans by specifying a larger number of parallel tasks. Note that increasing the number of tasks may increase server resource usage.
  • For more details, see:
    • RTX Parallel Scan (ja)

Client

• The \show table command in tgsql now displays primary key information for each table
• Tsubakuro: Added BASE64 as a column mapping method in LoadBuilder

Endpoint

• Automatically release related resources when a session ends
  • Previously, when forcibly terminating a session with tgctl session shutdown or when a client process was forcibly terminated, related transaction and statement resources might not be released, potentially affecting other transactions, especially those related to LTX. Now, related resources are automatically released when a session ends.
  • However, depending on how the client process is terminated, sessions may remain on the server. In such cases, the server's session timeout (default: 5 minutes) will release the session and related resources, which may result in a delay between client termination and resource release.

Distribution

• Changed supported platforms
  • (Experimental) AlmaLinux: updated from 9.5 to 9.6
  • (Experimental) Rocky Linux: updated from 9.5 to 9.6
• Added support for Clang 19 (previously supported up to Clang 18)
• Changed the JDK version installed by the installer from 11 to 17
  • Tsubakuro and Tanzawa included in the installer are built with JDK 11. If JDK 11 is not installed, Gradle's Java Toolchain will automatically download and use JDK 11 during the build.

Bug Fixes

SQL

• Fixed an issue where a SymbolAnalyzeException could occur if the SELECT list contained both aggregate functions and placeholders

Endpoint

• Fixed an issue where tgctl shutdown might not work correctly if session or transaction resources remained
  • Related to the above, tgctl shutdown may not complete until sessions released by session timeout are fully cleaned up

Transaction

• Fixed an issue where deleted records could be restored after running the online compaction tool, deleting records, and then restarting the database

Client

• Fixed an issue in Tsubakuro/Java where, if Long.MAX_VALUE milliseconds was specified as the session connection timeout for IPC connections, the second session connection could fail due to a timeout

Upgrade Notes

Client Compatibility List

Tsurugi 1.5.0 supports the following clients.
Please upgrade each client as needed when upgrading Tsurugi.

Client	Version
Tsubakuro/Java	1.10.0
Iceaxe	1.10.0
Tanzawa	1.10.0
Tsubakuro/Rust	0.3.0
Tsurugi MCP Server	0.2.0

Upgrade Procedure

For instructions on upgrading from previous versions, see:

• Tsurugi Upgrade Guide

Other Information

For a full list of changes in this version, see the Changelog:

• Tsurugi 1.5.0 - Changelog

For known issues and additional information about fixes in this version, see:

• Tsurugi 1.5.0 - Known Issues(en)