-
Notifications
You must be signed in to change notification settings - Fork 973
Release 2.22.0 #8536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.22.0 #8536
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 2.22.x #8536 +/- ##
==========================================
+ Coverage 82.37% 82.46% +0.08%
==========================================
Files 248 248
Lines 47622 47594 -28
Branches 12102 12098 -4
==========================================
+ Hits 39230 39249 +19
- Misses 3501 3510 +9
+ Partials 4891 4835 -56 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ccf8e59
to
e8b7084
Compare
e8b7084
to
8a8e3ef
Compare
4bc5651
to
8a8e3ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few nits.
Can you please include this #8517 into the release? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a summary of highlighted features in the changelog and would like input. It would be good to get a review from Philip when he's back as well.
630f6dc
to
90385fb
Compare
90385fb
to
8b58c07
Compare
8b58c07
to
020661d
Compare
6e80f3f
to
03a45e5
Compare
Co-authored-by: Iain Cox <[email protected]> Co-authored-by: Sven Klemm <[email protected]> Signed-off-by: Sven Klemm <[email protected]>
Co-authored-by: Iain Cox <[email protected]> Signed-off-by: Philip Krauss <[email protected]>
Signed-off-by: Philip Krauss <[email protected]>
Signed-off-by: Philip Krauss <[email protected]>
Signed-off-by: Philip Krauss <[email protected]>
03a45e5
to
888697d
Compare
Signed-off-by: Philip Krauss <[email protected]>
2.22.0 (2025-09-02)
This release contains performance improvements and bug fixes since the 2.21.3 release. We recommend that you upgrade at the next available opportunity.
Highlighted features in TimescaleDB v2.22.0
ALTER TABLE
rather than relying only on internal heuristics. Users can define indexes on multiple columns to improve query performance for their specific workloads.timescaledb.invalidate_using
option, enabling invalidations to be collected either via triggers on the hypertable or directly from WAL using logical decoding. Aggregates inherit the hypertable’s method if none is specified.timescaledb.enable_uuid_compression
) to simplify the downgrading experience, and will be enabled out of the box in the next minor release.uuid_timestamp()
returns a PostgreSQL timestamp from a UUIDv7.Removal of the hypercore table access method
We made the decision to deprecate the hypercore table access method (TAM) with the 2.21.0 release. Hypercore TAM was an experiment and it did not show the performance improvements we hoped for. It is removed with this release. Upgrades to 2.22.0 and higher are blocked if TAM is still in use. Since TAM’s inception in 2.18.0, we learned that btrees were not the right architecture. Recent advancements in the columnstore, such as more performant backfilling, SkipScan, adding check constraints, and faster point queries, put the columnstore close to or on par with TAM without needing to store an additional index. We apologize for the inconvenience this action potentially causes and are here to assist you during the migration process.
Migration path
Features
ALTER
options when encountering unsupported optionsDecompressChunk
custom node name toColumnarScan
ALTER TABLE RESET
for compression settingsNULL
_timescaledb_functions.chunk_status_text
helper functionBugfixes
columnstore=false
when using the TimescaleDB Apache 2 Editionnot null
constraint messagetimestamp out of range
usingend_offset=NULL
on CAgg refresh policyGUCs
enable_multikey_skipscan
: Enable SkipScan for multiple distinct keys, default: onenable_uuid_compression
: Enable UUID compression functionality, default: offcagg_processing_wal_batch_size
: Batch size when processing WAL entries, default: 10000cagg_processing_low_work_mem
: Low working memory limit for continuous aggregate invalidation processing, default: 38.4MBcagg_processing_high_work_mem
: High working memory limit for continuous aggregate invalidation processing, default: 51.2MBThanks
end_offset=NULL
on CAgg refresh policy