Release Notes 4.11

The 4.11 release notes were released on April 9th, 2025

Compatibility Matrix

System Requirement

Details

Supported OS

RHEL 8.9

supported Nvidia driver

CUDA version 12.3.2

Storage version

59

New Features and Enhancements

► SQDB’s new DATETIME2 data type delivers nanosecond precision and timezone notation, for reliable and accurate time-based data.

► Array decompress to run on GPU (Performance improvement).

Known Issues

Percentile is not supported for Window Functions

Version 4.11 resolved Issues

SQ No.

Description

SQ-18621

DELETE statement causes Worker stability issue

SQ-19275

Compression issue

SQ-19415

Problem granting column DDL privilege to new roles

SQ-19485

Issue using COPY FROM JSON file containing ARRAY data

SQ-19534

Issue with ARRAY containing large TEXT

SQ-19541

Issue using DISTINCT clause on ARRAY

SQ-19571

LZ4 is not permitted for FLOAT cell of ARRAY

SQ-19635

DICT Compression issue

SQ-19869

STDDEV functions slow compilation time

SQ-19879

Issue with Saved Queries Default permissions during database creation

Deprecation

► Haskell CLI

Starting October 2024, support for the Haskell CLI is discontinued, and it is replaced by the Multi Platform CLI that is compatible with the Haskell CLI with the added value of Table-View and cross platform compatability.

► CentOS Linux 7.x

  • As of June 2024, CentOS Linux 7.x has reached its End of Life and is no longer supported by SQreamDB.

► DateTime2 Alias

As of April 2025, the alias DateTime2 for the DateTime Data Type has been deprecated to simplify our data model and make way for the introduction of a new data type named DateTime2.

Upgrading to Version 4.11

  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.