Document Center

All Products

Document Center

Hologres:V4.0.32 Release Notes

Last Updated:Jun 29, 2026

Hologres V4.0.32 optimizes the Paimon cache policy and fixes issues including MemTable data loss, CPU spikes from empty ORC files, and Use-After-Free coredumps.

Enhancements

Paimon cache policy optimization: Adjusted the default Paimon manifest cache page size and disabled split cache by default to reduce unnecessary caching overhead.

Bug fixes

Severity	Title	Description	Affected versions	Workaround
P2	Fixed MemTable data loss when persisting a snapshot during target table queries.	Persisting a snapshot while querying a target table could cause MemTable data loss. This fix disables the persistence path.	V4.0 and later	Upgrade to V4.0.32 or a later version.
P2	Fixed a Paimon reader hang when reading a fully deleted Avro file.	The Paimon reader could hang when reading an Avro file fully marked for deletion.	V4.0 and later	Upgrade to V4.0.32 or a later version.
P2	Fixed 100% CPU utilization when getting the row count of an empty ORC file.	Getting the row count of an empty ORC file with zero stripes could trigger an infinite loop, driving a holo worker to 100% CPU and causing query hangs or failures.	V3.2 and later	Stop reading the corresponding table.
P2	Fixed a null pointer dereference in SPI_getvalue for empty result sets.	`SPI_getvalue` could trigger a null pointer dereference on an empty query result.	V4.0 and later	Upgrade to V4.0.32 or a later version.
P2	Fixed transaction abort hangs after a Change Data scan error.	During a concurrent Change Data scan of multiple ORC files, an underlying exception failed to wake waiting readers, causing transaction aborts to hang after a refresh error.	V3.1 and later	Terminate the hung worker.
P0	Fixed a Use-After-Free error caused by a lifecycle defect in ForeignTableExecutorAccessor.	A defect in shared_ptr lifecycle management within the `ForeignTableExecutorAccessor::GetNext` path could trigger a Use-After-Free error, causing a holo worker coredump.	V3.1 and later	Upgrade to V4.0.32 or a later version.
P2	Fixed a pointer escape issue in partition pruning when a prepared statement reused a CachedPlan.	When a prepared statement reused a CachedPlan, the partition pruning node wrote an invalid pointer. Subsequent execution could dereference this dangling pointer and trigger an FE coredump.	V4.0 and later	Upgrade to V4.0.32 or a later version.