2.19.3 (2025-04-15)
This release contains bug fixes since the 2.19.2 release. We recommend that you upgrade at the next available opportunity.
Bug fixes
- #7893 Don't capture hard errors in with-clause parser
- #7903 Don't capture hard errors for old cagg format
- #7912 Don't capture errors estimating time max spread
- #7910 Fix not using SkipScan over one chunk
- #7913 Allow TAM chunk creation as non-owner
- #7935 Fix TAM segfault on DELETE using segmentby column
- #7954 Allow scheduler restarts to be disabled
- #7964 Crash when grouping by multiple columns of a compressed table, one of which is a UUID segmentby column.
2.19.2 (2025-04-07)
This release contains bug fixes since the 2.19.1 release. We recommend that you upgrade at the next available opportunity.
Features
- #7923 Add a GUC to set a compression batch size limit
Bugfixes
GUCs
compression_batch_size_limit
: set batch size limit, default:1000
Thanks
- @soedirgo for reporting that published tables don't get dropped when they have a hypertable*
2.19.1 (2025-04-01)
This release contains bug fixes since the 2.19.0 release. We recommend that you upgrade at the next available opportunity.
Bugfixes
- #7816 Fix
ORDER BY
for direct queries on partial chunks - #7834 Avoid unnecessary scheduler restarts
- #7837 Ignore frozen chunks in compression policy
- #7850 Add
is_current_xact_tuple
to Arrow TTS - #7890 Flush error state before doing anything else
Thanks
- @bjornuppeke for reporting a problem with
INSERT INTO ... ON CONFLICT DO NOTHING
on compressed chunks - @kav23alex for reporting a segmentation fault on
ALTER TABLE
withDEFAULT
2.19.0 (2025-03-18)
This release contains performance improvements and bug fixes since the 2.18.2 release. We recommend that you upgrade at the next available opportunity.
- Improved concurrency of INSERT, UPDATE and DELETE operations on the columnstore by no longer blocking DML statements during the recompression of a chunk.
- Improved system performance during Continuous Aggregates refreshes by breaking them into smaller batches which reduces systems pressure and minimizes the risk of spilling to disk.
- Faster and more up-to-date results for queries against Continuous Aggregates by materializing the most recent data first (vs old data first in prior versions).
- Faster analytical queries with SIMD vectorization of aggregations over text columns and group by over multiple column
- Enable optimizing chunk size for faster query performance on the columnstore by adding support for merging columnstore chunks to the merge_chunk API.
Deprecation warning
This is the last minor release supporting PostgreSQL 14. Starting with the minor version of TimescaleDB only Postgres 15, 16 and 17 will be supported.
Downgrading of 2.19.0
This release introduces custom bool compression, if you enable this feature via the enable_bool_compression
and must downgrade to a previous, please use the following script to convert the columns back to their previous state. TimescaleDB versions prior to 2.19.0 do not know how to handle this new type.
Features
- #7586 Vectorized aggregation with grouping by a single text column.
- #7632 Optimize recompression for chunks without segmentby
- #7655 Support vectorized aggregation on Hypercore TAM
- #7669 Add support for merging compressed chunks
- #7701 Implement a custom compression algorithm for bool columns. It is experimental and can undergo backwards-incompatible changes. For testing, enable it using timescaledb.enable_bool_compression = on.
- #7707 Support ALTER COLUMN SET NOT NULL on compressed chunks
- #7765 Allow tsdb as alias for timescaledb in WITH and SET clauses
- #7786 Show warning for inefficient compress_chunk_time_interval configuration
- #7788 Add callback to mem_guard for background workers
- #7789 Do not recompress segmentwise when default order by is empty
- #7790 Add configurable Incremental CAgg Refresh Policy
Bugfixes
- #7665 Block merging of frozen chunks
- #7673 Don't abort additional INSERTs when hitting first conflict
- #7714 Fixes a wrong result when compressed NULL values were confused with default values. This happened in very special circumstances with alter table added a new column with a default value, an update and compression in a very particular order.
- #7747 Block TAM rewrites with incompatible GUC setting
- #7748 Crash in the segmentwise recompression
- #7764 Fix compression settings handling in Hypercore TAM
- #7768 Remove costing index scan of hypertable parent
- #7799 Handle DEFAULT table access name in ALTER TABLE
GUCs
enable_bool_compression
: enable the BOOL compression algorithm, default:OFF
enable_exclusive_locking_recompression
: enable exclusive locking during recompression (legacy mode), default:OFF
Thanks
- @bjornuppeke for reporting a problem with INSERT INTO ... ON CONFLICT DO NOTHING on compressed chunks
- @kav23alex for reporting a segmentation fault on ALTER TABLE with DEFAULT
2.18.2 (2025-02-19)
This release contains performance improvements and bug fixes since the 2.18.1 release. We recommend that you upgrade at the next available opportunity.
Bugfixes
- #7686 Potential wrong aggregation result when using vectorized aggregation with hash grouping in reverse order
- #7694 Fix ExplainHook breaking call chain
- #7695 Block dropping internal compressed chunks with
drop_chunk()
- #7711 License error when using hypercore handler
- #7712 Respect other extensions' ExecutorStart hooks
Thanks
- @davidmehren and @jflambert for reporting an issue with extension hooks
- @jflambert for reporting a bug with license errors shown in autovacuum
2.18.1 (2025-02-10)
This release contains performance improvements and bug fixes since the 2.18.0 release. We recommend that you upgrade at the next available opportunity.
Features
- https://github.com/timescale/timescaledb/pull/7656 Remove limitation of compression policy for continuous aggregates
Bugfixes
- https://github.com/timescale/timescaledb/pull/7600 Fix lock order when dropping index
- https://github.com/timescale/timescaledb/pull/7637 Allow EXPLAIN in read-only mode
- https://github.com/timescale/timescaledb/pull/7645 Fix DELETE on compressed chunk with non-btree operators
- https://github.com/timescale/timescaledb/pull/7649 Allow non-btree operator pushdown in UPDATE/DELETE queries on compressed chunks
- https://github.com/timescale/timescaledb/pull/7653 Push down orderby scankeys to Hypercore TAM
- https://github.com/timescale/timescaledb/pull/7665 Block merging of frozen chunks
- https://github.com/timescale/timescaledb/pull/7673 Don't abort additional INSERTs when hitting first conflict
GUCs
- enable_hypercore_scankey_pushdown: Push down qualifiers as scankeys when using Hypercore TAM introduced with https://github.com/timescale/timescaledb/pull/7653
Thanks
- @bjornuppeke for reporting a problem with INSERT INTO ... ON CONFLICT DO NOTHING on compressed chunks
- @ikalafat for reporting a problem with EXPLAIN in read-only mode
- Timescale community members Jacob and pantonis for reporting issues with slow queries.
2.18.0 (2025-01-23)
This release introduces the ability to add secondary indexes to the columnstore, improves group by and filtering performance through columnstore vectorization, and contains the highly upvoted community request of transition table support. We recommend that you upgrade at the next available opportunity.
Highlighted features in TimescaleDB v2.17.0
- The ability to add secondary indexes to the columnstore through the new hypercore table access method.
- Significant performance improvements through vectorization (
SIMD
) for aggregations using a group by with one column and/or using a filter clause when querying the columnstore. - Hypertables support triggers for transition tables, which is one of the most upvoted community feature requests.
- Updated methods to manage Timescale's hybrid row-columnar store (hypercore) that highlight the usage of the columnstore which includes both an optimized columnar format as well as compression.
Dropping support for Bitnami images
After the recent change in Bitnami’s LTS support policy, we are no longer building Bitnami images for TimescaleDB. We recommend using the official TimescaleDB Docker image
Deprecation Notice
We are deprecating the following parameters, functions, procedures and views. They will be removed with the next major release of TimescaleDB. Please find the replacements in the table below:
Deprecated | Replacement | Type |
---|---|---|
decompress_chunk | convert_to_rowstore | Procedure |
compress_chunk | convert_to_columnstore | Procedure |
add_compression_policy | add_columnstore_policy | Function |
remove_compression_policy | remove_columnstore_policy | Function |
hypertable_compression_stats | hypertable_columnstore_stats | Function |
chunk_compression_stats | chunk_columnstore_stats | Function |
hypertable_compression_settings | hypertable_columnstore_settings | View |
chunk_compression_settings | chunk_columnstore_settings | View |
compression_settings | columnstore_settings | View |
timescaledb.compress | timescaledb.enable_columnstore | Parameter |
timescaledb.compress_segmentby | timescaledb.segmentby | Parameter |
timescaledb.compress_orderby | timescaledb.orderby | Parameter |
Features
- #7341: Vectorized aggregation with grouping by one fixed-size by-value compressed column (such as arithmetic types).
- #7104: Hypercore table access method.
- #6901: Add hypertable support for transition tables.
- #7482: Optimize recompression of partially compressed chunks.
- #7458: Support vectorized aggregation with aggregate
filter
clauses that are also vectorizable. - #7433: Add support for merging chunks.
- #7271: Push down
order by
in real-time continuous aggregate queries. - #7455: Support
drop not null
on compressed hypertables. - #7295: Support
alter table set access method
on hypertable. - #7411: Change parameter name to enable hypercore table access method.
- #7436: Add index creation on
order by
columns. - #7443: Add hypercore function and view aliases.
- #7521: Add optional
force
argument torefresh_continuous_aggregate
. - #7528: Transform sorting on
time_bucket
to sorting on time for compressed chunks in some cases. - #7565: Add hint when hypertable creation fails.
- #7390: Disable custom
hashagg
planner code. - #7587: Add
include_tiered_data
parameter toadd_continuous_aggregate_policy
API. - #7486: Prevent building against PostgreSQL versions with broken ABI.
- #7412: Add GUC for the
hypercore_use_access_method
default. - #7413: Add GUC for segmentwise recompression.
Bugfixes
- #7378: Remove obsolete job referencing
policy_job_error_retention
. - #7409: Update
bgw_job
table when altering procedure. - #7410: Fix the
aggregated compressed column not found
error on aggregation query. - #7426: Fix
datetime
parsing error in chunk constraint creation. - #7432: Verify that the heap tuple is valid before using.
- #7434: Fix the segfault when internally setting the replica identity for a given chunk.
- #7488: Emit error for transition table trigger on chunks.
- #7514: Fix the error:
invalid child of chunk append
. - #7517: Fix the performance regression on the
cagg_migrate
procedure. - #7527: Restart scheduler on error.
- #7557: Fix null handling for in-memory tuple filtering.
- #7566: Improve transaction check in CAGG refresh.
- #7584: Fix NaN-handling for vectorized aggregation.
Thanks
- @bharrisau for reporting the segfault when creating chunks.
- @k-rus for suggesting that we add a hint when hypertable creation fails.
- @pgloader for reporting the issue in an internal background job.
- @staticlibs for sending the pull request that improves the transaction check in CAGG refresh.
- @uasiddiqi for reporting the
aggregated compressed column not found
error.
2.17.2
This release contains bug fixes since the 2.17.1 release. We recommend that you upgrade at the next available opportunity.
Bugfixes
- #7384 Fix "negative bitmapset member not allowed" and performance degradation on queries to compressed tables with ORDER BY clause matching the order of the compressed data
- #7388 Use-after-free in vectorized grouping by segmentby columns
Thanks
- @dx034 for reporting an issue with negative bitmapset members due to large OIDs
2.17.1 (2024-10-21)
This release contains performance improvements and bug fixes since the 2.17.0 release. We recommend that you upgrade at the next available opportunity.
Features
- #7360 Add chunk skipping GUC
Bugfixes
- #7335 Change log level used in compression
- #7342 Fix collation for in-memory tuple filtering
Thanks
- @gmilamjr for reporting an issue with the log level of compression messages
- @hackbnw for reporting an issue with collation during tuple filtering
2.17.0 (2024-10-08)
This release adds support for PostgreSQL 17, significantly improves the performance of continuous aggregate refreshes, and contains performance improvements for analytical queries and delete operations over compressed hypertables. We recommend that you upgrade at the next available opportunity.
Highlighted features in TimescaleDB v2.17.0
-
Full PostgreSQL 17 support for all existing features. TimescaleDB v2.17 is available for PostgreSQL 14, 15, 16, and 17.
-
Significant performance improvements for continuous aggregate policies: Continuous aggregate refresh is now using
merge
instead of deleting old materialized data and re-inserting. This update can decrease dramatically the amount of data that must be written on the continuous aggregate in the presence of a small number of changes, reduce thei/o
cost of refreshing a continuous aggregate, and generate fewer Write-Ahead Logs (WAL
). Overall, continuous aggregate policies will be more lightweight, use less system resources, and complete faster. -
Increased performance for real-time analytical queries over compressed hypertables: We are excited to introduce additional Single Instruction, Multiple Data (
SIMD
) vectorization optimization to our engine by supporting vectorized execution for queries that group by using thesegment_by
column(s) and aggregate using the basic aggregate functions (sum
,count
,avg
,min
,max
). Stay tuned for more to come in follow-up releases! Support for grouping on additional columns, filtered aggregation, vectorized expressions, andtime_bucket
is coming soon. -
Improved performance of deletes on compressed hypertables when a large amount of data is affected. This improvement speeds up operations that delete whole segments by skipping the decompression step. It is enabled for all deletes that filter by the
segment_by
column(s).
PostgreSQL 14 deprecation announcement
We will continue supporting PostgreSQL 14 until April 2025. Closer to that time, we will announce the specific version of TimescaleDB in which PostgreSQL 14 support will not be included going forward.
Features
- https://github.com/timescale/timescaledb/pull/6882: Allow delete of full segments on compressed chunks without decompression.
- https://github.com/timescale/timescaledb/pull/7033: Use
merge
statement on continuous aggregates refresh. - https://github.com/timescale/timescaledb/pull/7126: Add functions to show the compression information.
- https://github.com/timescale/timescaledb/pull/7147: Vectorize partial aggregation for
sum(int4)
with grouping onsegment by
columns. - https://github.com/timescale/timescaledb/pull/7204: Track additional extensions in telemetry.
- https://github.com/timescale/timescaledb/pull/7207: Refactor the
decompress_batches_scan
functions for easier maintenance. - https://github.com/timescale/timescaledb/pull/7209: Add a function to drop the
osm
chunk. - https://github.com/timescale/timescaledb/pull/7275: Add support for the
returning
clause formerge
. - https://github.com/timescale/timescaledb/pull/7200: Vectorize common aggregate functions like
min
,max
,sum
,avg
,stddev
,variance
for compressed columns of arithmetic types, when there is grouping onsegment by
columns or no grouping.
Bug fixes
- https://github.com/timescale/timescaledb/pull/7187: Fix the string literal length for the
compressed_data_info
function. - https://github.com/timescale/timescaledb/pull/7191: Fix creating default indexes on chunks when migrating the data.
- https://github.com/timescale/timescaledb/pull/7195: Fix the
segment by
andorder by
checks when dropping a column from a compressed hypertable. - https://github.com/timescale/timescaledb/pull/7201: Use the generic extension description when building
apt
andrpm
loader packages. - https://github.com/timescale/timescaledb/pull/7227: Add an index to the
compression_chunk_size
catalog table. - https://github.com/timescale/timescaledb/pull/7229: Fix the foreign key constraints where the index and the constraint column order are different.
- https://github.com/timescale/timescaledb/pull/7230: Do not propagate the foreign key constraints to the
osm
chunk. - https://github.com/timescale/timescaledb/pull/7234: Release the cache after accessing the cache entry.
- https://github.com/timescale/timescaledb/pull/7258: Force English in the
pg_config
command executed bycmake
to avoid the unexpected building errors. - https://github.com/timescale/timescaledb/pull/7270: Fix the memory leak in compressed DML batch filtering.
- https://github.com/timescale/timescaledb/pull/7286: Fix the index column check while searching for the index.
- https://github.com/timescale/timescaledb/pull/7290: Add check for null offset for continuous aggregates built on top of continuous aggregates.
- https://github.com/timescale/timescaledb/pull/7301: Make foreign key behavior for hypertables consistent.
- https://github.com/timescale/timescaledb/pull/7318: Fix chunk skipping range filtering.
- https://github.com/timescale/timescaledb/pull/7320: Set the license specific extension comment in the install script.
Thanks
- @MiguelTubio for reporting and fixing the Windows build error.
- @posuch for reporting the misleading extension description in the generic loader packages.
- @snyrkill for discovering and reporting the issue with continuous aggregates built on top of continuous aggregates.