Tsurugi 1.0.0-BETA6 - Release Notes (en)

[akirakw]

1.0.0-BETA6 Release Notes

Overview

In this version, we have mainly added and improved SQL features.

Additionally, several important configuration and incompatible changes have been made. Please see "Configuration Changes and Incompatible Changes".

Feature Additions and Improvements

• SQL

  • Support for INSERT INTO SELECT statements

    • INSERT INTO ... SELECT ...
    • INSERT OR REPLACE INTO ... SELECT ...
    • INSERT OR IGNORE INTO ... SELECT ...

  • Support for BINARY and VARBINARY types

    • Support for basic functionalities such as SELECT/INSERT/UPDATE/DELETE statements, ORDER BY clause, comparisons, and casting
    • Support for binary literals and registering binary data via client API placeholders
    • Support for displaying binary types in tgsql
    • This version has the following limitations:
      • VARBINARY type cannot be used as a primary key or index key column
      • Not supported for dump/load operations

  • Support for date/time functions

    • CURRENT_DATE
    • LOCALTIME
    • CURRENT_TIMESTAMP
    • LOCALTIMESTAMP

  • Support for date/time literals

    • DATE 'YYYY-MM-DD'
    • TIME 'HH:MM:SS'
    • TIMESTAMP 'YYYY-MM-DD HH:MM:SS'
    • TIMESTAMP WITH TIME ZONE 'YYYY-MM-DD HH:MM:SS+HH:MM'
    • (Casting between string types and date/time types will be supported in future versions)

  • Column default values in CREATE TABLE now can accept date time functions

    • CREATE TABLE t ( ..., ts TIMESTAMP WITH TIME ZONE DEFAULT CURRENT_TIMESTAMP )

  • Support BETWEEN predicate

  • Support IN predicate

    • In this version, only IN predicate with value list (e.g., x IN (a, b, c)) is enabled

  • Increased the maximum definable size for CHAR and VARCHAR types (excluding columns specified as primary keys or indexes) from approximately 30KB to approximately 2MB

    • The same applies to BINARY and VARBINARY types
    • When using IPC endpoints, note that the result set size of SELECT statements is constrained by the ipc_endpoint.datachannel_buffer_size setting.
      • For details, refer to the Tsurugi Troubleshooting Guide.

  • Correct TIMESTAMP WITH TIMEZONE type to consider its zone offset (e.g., +09:00)

• Endpoint

  • Support for automatic session timeout and Keep Alive from the client
    • This feature enables automatically disconnecting sessions inactive for a period of time, and will release their resources.
    • In order to prevent unintentional session disconnections, this version includes that clients can periodically send keep alive messages (enabled by default).
      • Keep Alive messages are enabled from Tsubakuro 1.5.0 and libraries using it. Note that older versions of the client do not send Keep Alive messages.
    • The settings for automatic session timeout can be changed in the session section of the configuration definition file tsurugi.ini.

• Server Configurations (New options that can be specified in tsurugi.ini)

  • session.zone_offset
    • Specifies the default time zone offset for sessions as an ISO8601 compliant string (e.g., ±[hh]:[mm] or Z). The default is the string indicating UTC.

For details on SQL features, refer to Available SQL features in Tsurugi.

Configuration Changes and Incompatible Changes

In this version, the following configuration changes and incompatible changes against previous versions of Tsurugi have been made.

• TCP endpoints are disabled by default

  • Mainly for security reasons, TCP endpoints are disabled by default. To use TCP endpoints, set stream_endpoint.enabled to true in tsurugi.ini.
  • On the Tsurugi Docker image, TCP endpoints are enabled by default as before.

• Removed old SQL compiler (Shakujo Compiler)

  • The old SQL compiler (Shakujo Compiler) and its dependent modules have been excluded from the installation configuration.
  • The setting to enable the old SQL compiler with sql.dev_compiler_support=0 in tsurugi.ini has been removed.

• Configuration changes for Ogawayama

  • Due to the review of the release configuration by organizing module dependencies, "Ogawayama Stub" and its dependent modules have been excluded from the installation configuration. Ogawayama Stub is a dependent module of tsurugi_fdw and is unnecessary if not used.
  • The Ogawayama module "Ogawayama Bridge," which operates as part of the Tsurugi server, is still included in the tsurugidb installation.

• Changes to the directory structure of the installation archive

  • When extracting the installation archive, a tsurugidb-<version> directory is created at the first level, and any resources are placed under it.

Bug Fixes

• SQL

  • Incorrect results may be returned when the same aggregate function is written twice in the SELECT list.
  • The max and min functions for DECIMAL columns with precision 0 may return incorrect results.
  • The results of the max and min functions for the TIMESTAMP WITH TIME ZONE type become the TIMESTAMP type.

• Transaction

  • Serializability violations may not be detected in specific cases involving conflicts of three or more LTX.
  • Deleted records may be readable in specific cases involving conflicts of multiple OCC and LTX.
  • Unexpected errors or stalls may occur when INSERT OR REPLACE and INSERT conflict with multiple OCC.
  • If an I/O error occurs during tsurugidb startup, such as exceeding limit on the number of file opens, the database contents may be restored incorrectly.
    • Related: Tsurugi Troubleshooting Guide
  • Shutdown may not complete normally after creating a large number of tables.

• Endpoint

  • No response is returned if the result set size exceeds ipc_endpoint.datachannel_buffer_size when executing SELECT via IPC connection.

• Client APIs

  • Abnormal values may occur when registering values via API placeholders for the TIMESTAMP WITH TIME ZONE type.

---

Various other stability improvements and operational enhancements have been made.
For more details, please refer to the following changelog:

• Tsurugi 1.0.0-BETA6 - Changelog

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

• Tsurugi Upgrade Guide

---

This discussion was created from the release 1.0.0-BETA6.