Release Notes 4.18

The 4.18 release notes were released on October 30, 2026

Compatibility Matrix

System Requirement

Details

Supported OS

RHEL 8.9 / 8.10 / 9.5 / 9.6

supported Nvidia driver

CUDA version 12.3.2 / 12.6.1 / 12.9.1 / 13.0

Storage version

102

New Features

► PIVOT ARRAY and PIVOT DISTINCT ARRAY accept a subquery in place of the list of values to pivot on. Please see PIVOT ARRAY with a value query.

► New SHOW_STUCK_UNLINKS utility function lists deleted files whose removal from disk has failed. Please see SHOW_STUCK_UNLINKS.

Known Issues

Using Grant operation on a specific UDF function fail.

Percentile is not supported for Window Functions

The Node.JS connector does not support ARRAY data types.

Version 4.18 resolved Issues

SQ No.

Description

SQ-20823

Data sorting query failed in particular circumstances

SQ-22773

Files left in the table folder after DROP TABLE are now removed from disk

SQ-22929

Improved performance of queries that keep a small number of rows from each chunk

SQ-23036

Improved catalog table query performance

SQ-23290

PIVOT ARRAY now accepts a subquery as its list of values

SQ-23297

Deleted files are now removed from disk after a worker disconnects

SQ-23331

Improved chunk skipping on TEXT columns, for consistent query performance

SQ-23334

Further improved performance of queries that keep a small number of rows from each chunk

SQ-23361

Metadata of deleted chunks is now cleaned up

SQ-23372

Improved performance of queries running in parallel

SQ-23373

Improved query performance on tables sorted with CLUSTER BY

Deprecation

► No deprecations in this version.

Upgrading to Version 4.18

Upgrading to this version requires an additional infrastructure, to support some of it’s functionality. The requirements are listed below. In addition, it is required to perform a storage upgrade according to the listed process.

Additional packages

Please see additional installation requirements for In-process functions in this page

Storage upgrade

► Running storage upgrade and metadata backup listed below are mandatory for this version

  1. Generate a back-up of the metadata by running the following command:

    select backup_metadata('out_path');

    Tip

    SQreamDB recommends storing the generated back-up locally in case needed.

    SQreamDB runs the Garbage Collector and creates a clean backup tarball package.

  2. Shut down all SQreamDB services.

  3. Copy the recently created back-up file.

  4. Replace your current metadata with the metadata you stored in the back-up file.

  5. Navigate to the new SQreamDB package bin folder.

  6. Run the following command:

    ./upgrade_storage <levelDB path>

Note

Upgrading from a major version to another major version requires you to follow the Upgrade Storage step. This is described in Step 7 of the Upgrading SQreamDB Version procedure.