-
Notifications
You must be signed in to change notification settings - Fork 900
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.16.0 #7135
Closed
Closed
Release 2.16.0 #7135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This release contains performance improvements and bug fixes since the 2.15.3 release. We recommend that you upgrade at the next available opportunity. **Features** * timescale#6880: Add support for the array operators used for compressed DML batch filtering. * timescale#6895: Improve the compressed DML expression pushdown. * timescale#6897: Add support for replica identity on compressed hypertables. * timescale#6918: Remove support for PG13. * timescale#6920: Rework compression activity wal markers. * timescale#6989: Add support for foreign keys when converting plain tables to hypertables. * timescale#7020: Add support for the chunk column statistics tracking. * timescale#7048: Add an index scan for INSERT DML decompression. * timescale#7075: Reduce decompression on the compressed INSERT. * timescale#7101: Reduce decompressions for the compressed UPDATE/DELETE. * timescale#7108 Reduce decompressions for INSERTs with UNIQUE constraints **Bugfixes** * timescale#7018: Fix `search_path` quoting in the compression defaults function. * timescale#7046: Prevent locking for compressed tuples. * timescale#7055: Fix the `scankey` for `segment by` columns, where the type `constant` is different to `variable`. * timescale#7064: Fix the bug in the default `order by` calculation in compression. * timescale#7069: Fix the index column name usage. * timescale#7074: Fix the bug in the default `segment by` calculation in compression. **Thanks**
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7135 +/- ##
==========================================
+ Coverage 80.06% 81.78% +1.71%
==========================================
Files 190 203 +13
Lines 37181 38035 +854
Branches 9450 9872 +422
==========================================
+ Hits 29770 31106 +1336
+ Misses 2997 2965 -32
+ Partials 4414 3964 -450 ☔ View full report in Codecov by Sentry. |
iroussos
reviewed
Jul 19, 2024
To match the current ones in main.
To CHANGELOG.md. Patch from Yannis Roussos
pallavisontakke
requested review from
svenklemm,
antekresic,
fabriziomello,
billy-the-fish and
iroussos
July 24, 2024 08:12
svenklemm
approved these changes
Jul 24, 2024
iroussos
reviewed
Jul 24, 2024
in CHANGELOG.md. Patch from Iain.
iroussos
approved these changes
Jul 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This release contains performance improvements and bug fixes since
the 2.15.3 release. We recommend that you upgrade at the next
available opportunity.
In TimescaleDB v2.16.0 we:
Introduce a lot of performance focused optimizations for data manipulation operations (DML) over compressed chunks.
Speed up those tricky queries that access more chunks than needed.
TimescaleDB v2.16.0 extends chunk exclusion on compressed hypertables and is able to take into account
filters on additional, non-partitioning columns.
Offer new options for Timescale users who like their foreign keys.
You can now add foreign keys from regular tables towards hypertables. We have also removed
some really annoying locks in the reverse direction that blocked access to referenced tables
while compression was running.
Have big updates on the Continuous Aggregates front.
More types of joins are supported, additional equality operators on join clauses, and support for joins
between multiple regular tables.
Highlighted features in this release
Improved query performance through chunk exclusion on compressed hypertables.
You can now define sparse indexes on compressed chunks for any column with one of the following
integer data types:
smallint
,int
,bigint
,serial
,bigserial
,date
,timestamp
,timestamptz
.After you call
enable_column_stats
on a column, TimescaleDB tracks the min and max values forthat column. TimescaleDB uses that information to exclude chunks for queries that filter on that
column, and would not find any data in those chunks.
Improved upsert performance on compressed hypertables.
By using index scans to verify constraints during inserts on compressed chunks, TimescaleDB speeds
up some ON CONFLICT clauses by more than 100x.
Improved performance of updates, deletes, and inserts on compressed hypertables.
By filtering data while accessing the compressed data and before decompressing, TimescaleDB has
improved performance for updates and deletes on all types of compressed chunks, as well as inserts
into compressed chunks with unique constraints.
By signaling constraint violations without decompressing, or decompressing only when matching
records are found in the case of updates, deletes and upserts, TimescaleDB v2.16.0 speeds
up those operations more than 1000x in some update/delete scenarios, and 10x for upserts.
You can add foreign keys from regular tables to hypertables, with support for all types of cascading options.
This is useful for hypertables that partition using sequential IDs, and need to reference those IDs from other tables.
Lower locking requirements during compression for hypertables with foreign keys
Advanced foreign key handling removes the need for locking referenced tables when new chunks are compressed.
DML is no longer blocked on referenced tables while compression runs on a hypertable.
Improved support for queries on Continuous Aggregates
INNER/LEFT
andLATERAL
joins are now supported. Plus, you can now join with multiple regular tables,and you can have more than one equality operator on join clauses.
PostgreSQL 13 support removal announcement
Following the deprecation announcement for PostgreSQL 13 in TimescaleDB v2.13,
PostgreSQL 13 is no longer supported in TimescaleDB v2.16.
The Currently supported PostgreSQL major versions are 14, 15 and 16.
Features
Bugfixes
search_path
quoting in the compression defaults function.scankey
forsegment by
columns, where the typeconstant
is different tovariable
.order by
calculation in compression.segment by
calculation in compression.