All Products
Search
Document Center

Hologres:V4.1.21 Release Notes

Last Updated:Jun 29, 2026

Hologres V4.1.21 includes bug fixes for instance stability, query correctness, and performance.

Bug fixes

Severity

Title

Description

Affected versions

Workaround

P1

Fixed a Coredump that occurred in specific scenarios.

Instances could experience a Coredump.

V3.2 and later

Upgrade to V4.1.21 or later.

P2

Fixed a PgQueryExecutor destructor issue that triggered PANIC and a Coredump when the transaction had already been committed.

Instances could experience a Coredump.

V4.0 and later

P2

Fixed an issue where PQE SQL generation produced incorrect columns in subqueries.

Queries failed with column does not exist error.

V4.0 and later

P2

Fixed incorrect memory accounting in auto dictionary encoding mode that could cause out-of-memory (OOM) errors.

The system could experience out-of-memory (OOM) errors.

V4.1 and later

P2

Fixed incorrect validation logic for the memtable partition count limit.

Write operations could be incorrectly rejected.

V4.1 and later

P2

Fixed an issue where the LIMIT clause incorrectly restricted max_dop when the estimated row count was high.

Query parallelism could be unnecessarily limited, which degraded performance.

V4.0 and later

P2

Fixed a Binlog replay delay that occurred when rebuilding Binlog-enabled tables through the Dynamic Table optimization path.

Binlog replay could experience delays.

V4.0 and later

P2

Fixed suboptimal Parquet page filter performance for IN point lookups on composite primary keys.

Point lookup performance could fall below expectations.

V4.0 and later

P2

Fixed a recursive Coredump caused by an OnTransactionEnd error during nested transaction completion.

Instances could experience a Coredump.

V4.1 and later

P1

Fixed a stream resource leak that occurred when switching to batch mode or dropping a table immediately after a partition driver fallback.

Stream resources could leak.

V4.0 and later

P1

Fixed an issue where the max_pt function intermittently returned incorrect results in multi-level partition scenarios.

Querying external tables through max_pt could fail to retrieve the latest partition.

V4.0 and later

P2

Fixed a PQE stop race condition that caused connection errors.

The QE side could receive an ERPC_ERROR_CONNECTION_CLOSED error.

V4.0 and later