2.28.3
2.28.3 (2026-07-16)
Fixed 10
- Wrong result when evaluating a function returning NULL in the columnar query execution pipeline
- Incorrect usage of sort transformation for sort key expressions with negative constants
- Allow enabling and disabling triggers on hypertables with columnstore enabled
- Columnstore sort pushdown to check for different query sort key collation
- Potentially wrong results for stddev(float4) and stddev(float8) when used with avg() in the columnar query execution pipeline
- Race condition when enabling compression on a hypertable
- Batch filtering for compressed DML should respect collation
- Direct delete failed to handle array predicates with NULL values and deleted more rows than intended
- Reuse existing dimension_slice IDs when possible
- Truncate constraint name before trying to rename
This release contains performance improvements and bug fixes since the 2.28.2 release. We recommend that you upgrade at the next available opportunity.
Bugfixes
- #10082 Wrong result when evaluating a function returning
NULLin the columnar query execution pipeline - #10178 Fix incorrect usage of sort transformation for sort key expressions with negative constants
- #10179 Allow enabling and disabling triggers on hypertables with columnstore enabled
- #10182 Fix columnstore sort pushdown to check for different query sort key collation
- #10209 Fix potentially wrong results for
stddev(float4)andstddev(float8)when used withavg()in the columnar query execution pipeline - #10212 Fix race condition when enabling compression on a hypertable
- #10230 Batch filtering for compressed
DMLshould respect collation - #10254 Direct delete failed to handle array predicates with
NULLvalues and deleted more rows than intended (#10129) - #10257 Reuse existing
dimension_sliceIDs when possible - #10265 Truncate constraint name before trying to rename
Thanks
- @juantxorena for reporting that triggers could not be enabled or disabled on hypertables with columnstore enabled