Skip to content

chore(deps): update dependency timescale/timescaledb to v2.27.1#15

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/timescale-timescaledb-2.x
Open

chore(deps): update dependency timescale/timescaledb to v2.27.1#15
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/timescale-timescaledb-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 15, 2026

This PR contains the following updates:

Package Update Change
timescale/timescaledb minor 2.26.22.27.1

Release Notes

timescale/timescaledb (timescale/timescaledb)

v2.27.1

Compare Source

This release contains performance improvements and bug fixes since the 2.27.0 release. We recommend that you upgrade at the next available opportunity.

Bugfixes

  • #​9795 Delete orphaned compression_settings before migrating catalog table
  • #​9799 Fix job_errors view leaking failed jobs to non-owners
  • #​9800 Check hypertable ownership before recompression
  • #​9801 Fix information leak in policy_reorder_remove
  • #​9824 Adding migration scripts for composite bloom filters
  • #​9828 Skip columnar index scan when grouping by an expression
  • #​9830 Skip ColumnarIndexScan for GROUPING SETS / ROLLUP / CUBE

Thanks

  • @​homanp for reporting an information leak with the job_errors view

v2.27.0

Compare Source

This release contains performance improvements and bug fixes since the 2.26.4 release. We recommend that you upgrade at the next available opportunity.

Highlighted features in TimescaleDB v2.27.0

  • The Hypercore engine now supports a vectorized implementation of filters by evaluating them inline through the standard Postgres function path. This expands the set of queries (including continuous aggregate refreshes) that can take the faster path through the columnstore, yielding speedups ranging from 30% up to 2x in benchmarks.
  • UPDATE and DELETE statements with equality predicates can now use bloom filters to skip decompressing batches whose compressed rows can't match. When multiple bloom filters apply, they are evaluated in decreasing order of column count (most selective first), and EXPLAIN now reports filtering activity via the new "Compressed batches filtered" and "Batches filtered after decompression counters". The query performance increases in some case up to 160 times.
  • UPSERT queries can now leverage bloom filters (including composite ones) to skip decompressing batches when the arbiter values are guaranteed not to be present, with the most-selective filter chosen automatically when multiple apply. EXPLAIN output adds new statistics — batches checked by bloom, batches pruned by bloom, batches without bloom, and bloom false positives — for visibility into pruning effectiveness.

Upcoming PostgreSQL 15 EOL announcement
As a reminder, the upcoming TimescaleDB release in June 2026 will officially be the last version with support for PostgreSQL 15. This deprecation was initially announced in the v2.23.0 changelog on October 29, 2025, to provide users ample time to prepare. To ensure uninterrupted access to new features, bugfixes and performance enhancements, all instances must be upgraded to PostgreSQL 16 or greater.

Backward-Incompatible Changes

  • #​9579 The bloom filter sparse indexes on compressed int2 columns could lead to SELECT queries not returning the rows that actually match the WHERE condition. The upgrade is blocked for the affected databases, and the incorrect indexes have to be dropped manually before the upgrade.
  • This release introduces a new naming convention for composite bloom filter metadata. While this change will not disrupt query processing, v2.27 cannot automatically utilize composite bloom filters generated in v2.26. To convert your existing v2.26 composite bloom filters, the legacy metadata columns must be renamed. This is a lightweight, catalog-only operation requiring zero data recompression, which can be done with this migration script.

Features

  • #​8868 Use PG_MODULE_MAGIC_EXT for PG18
  • #​8967 Rewriting queries with continuous aggregates exactly matching query aggregation
  • #​9192 Push down scalar array operations into the columnar metadata scan by transforming them into an OR/AND clause.
  • #​9355 Defer segmentby default for direct compress
  • #​9374 Use bloom filters to eliminate decompression of unrelated compressed batches during UPSERTs.
  • #​9396 Analyze and get segmentby during direct compress
  • #​9398 Fix chunk exclusion for IN/ANY on open (time) dimensions
  • #​9399 Use bloom filters to reduce decompression during UPDATE/DELETE commands.
  • #​9403 Set default segmentby during direct compress flush
  • #​9437 Allow running compression as part of refresh policy for compressed continuous aggregates
  • #​9443 Enable vectorized aggregation in some cases when the WHERE clause contains filters not handled through the "Vectorized Filters" facility. This includes e.g. filters on time_bucket().
  • #​9458 Remove _timescaledb_functions.repair_relation_acls
  • #​9475 Calculate hashes for bloom filter predicates at planning time.
  • #​9504 Allow ALTER TABLE RESET on materialization hypertables
  • #​9521 Add support for reporting index creation progress
  • #​9559 Notice on compression settings change
  • #​9569 For nullable orderby columns do segmentwise decompress-compress instead of segmentwise recompress.
  • #​9583 Drop existing sparse indexes when dropping columns
  • #​9648 Support ENABLE/DISABLE TRIGGER on hypertables
  • #​9702 Allow Batch Sorted Merge for unordered chunks with no segmentby or when all segmentby columns are pinned to a Const

Bugfixes

  • #​9363 Change compression job status when chunks could be compressed
  • #​9413 Fix incorrect decompress markers on full batch delete
  • #​9414 Fix NULL compression handling in estimate_uncompressed_size
  • #​9417 Fix segfault in bloom1_contains
  • #​9479 Disallow sub-day offset for time-bucket on Date
  • #​9482 Forbid Batch Sort Merge on nullable orderby columns
  • #​9490 Disallow negative interval as chunk_interval
  • #​9500 Fix off-by-one error when building object name
  • #​9519 Remove self-referential FOREIGN KEY constraints from catalog
  • #​9561 Simplify job history retention by replacing binary search and temp table
  • #​9590 Fix policy skipping uncompressed chunks
  • #​9596 Remove unused process_hypertable_invalidations policy code
  • #​9604 Remove dead post_parse_analyze_hook capture in loader
  • #​9610 Fix use-after-free crash in cache_destroy during transaction abort
  • #​9632 Preserve chunk settings during recompress
  • #​9640 Fix NULL datumCopy crash in segmentby analysis
  • #​9680 Fix segfault in direct compress insert on hypertable with dropped column
  • #​9692 Fix internal "invalid perminfoindex 0 in RTE" error on MERGE NOT MATCHED INSERT into a hypertable
  • #​9705 Avoid double TOAST delete when DELETE-after-compression is enabled
  • #​9705 Only freeze compressed rows when truncating uncompressed chunk
  • #​9706 Use bigint in estimate_uncompressed_size calculations
  • #​9709 Reject mismatched element type in bool/uuid decompression
  • #​9710 Return bigint from compressed_data_column_size
  • #​9711 Fix registration row leak when continuous aggregate refresh fails
  • #​9697 Improve pathkey handling for compressed sub-paths during sort transformation
  • #​9743 Fix the composite bloom metadata column naming scheme
  • #​9767 Skip dropped chunks when trying to remove ts_cagg_invalidation_trigger
  • #​9747 Reject inheriting from a hypertable
  • #​9744 Use a fixed call string for the telemetry job in ts_stat_statements recording
  • #​9736 Do logical sparse index comparison
  • #​9731 Avoid creating overlapping batches during recompression for multi orderby configurations
  • #​9717 Reject non-positive time bucket width on cagg creation
  • #​9707 Fix policy name comparison in remove_policies

New Settings

  • enable_cagg_rewrites: enables rewriting queries with CAggs. Off by default. cagg_rewrites_debug_info: prints CAgg rewrites diagnostics. Off by default.
  • enable_columnar_scan_filter_pushdown: enables pushing the filters on columnar scan down to the compressed scan level. On by default.

Thanks

v2.26.4

Compare Source

This release contains bug fixes since the 2.26.3 release. We recommend that you upgrade at the next available opportunity.

Bugfixes

  • #​9360 Sanitize DT_NOBEGIN next_start to recover jobs stuck after primary failover
  • #​9515 Fix now() constification for continuous aggregate queries
  • #​9550 Fix out of memory when propagating ALTER TABLE to many chunks
  • #​9605 Fix InstrStartNode called twice in a row
  • #​9607 Fix use-after-free of PlaceHolderVar.phrels in cached ChunkAppend plans
  • #​9612 Fix PlaceHolderVar error in runtime chunk exclusion
  • #​9614 Remove stale hypertable entries during upgrade
  • #​9615 Fix segfault with transition tables after column drop
  • #​9616 Use DROP CASCADE for trigger removal
  • #​9623 Error when querying compressed chunks under Apache license
  • #​9625 Make timescaledb_post_restore() reliably restart background workers in a single call
  • #​9639 Fix lost orderby sparse index
  • #​9646 Replace ERRCODE_INTERNAL_ERROR on user-reachable error paths
  • #​9652 Add Error on missing custom job function in ts_bgw_job_get_funci
  • #​9655 Fix data corruption when merging chunks with different compression settings
  • #​9654 Fix sort_transform crash with hypertable on nullable side of outer join
  • #​9656 Fix concurrent merge of compressed chunks dropping the new heap
  • #​9641 Fix COPY path with transition tables after column drop
  • #​9660 Fix incremental continuous aggregate refresh so that extend_last_bucket only applies to the boundary batch
  • #​9674 Fix segmentby crash in cagg invalidation tracking

Thanks

  • @​GetsuDer and @​WeiJie-JL for reporting an error with timescaledb and extensions using Explain
  • @​igor2x for reporting a problem when trying to query compressed data with the Apache license
  • @​ivaaaan for reporting an issue with constraint pushdown in continuous aggregate queries
  • @​patstrom for reporting a segfault with transition table triggers after dropping a column
  • @​patstrom for reporting an out-of-memory error when dropping constraints
  • @​pcayen for reporting an issue with GROUP BY ROLLUP on views over hypertables

v2.26.3

Compare Source

This release contains bug fixes since the 2.26.2 release. We recommend that you upgrade at the next available opportunity.

Bugfixes

  • #​9511 Fix alter_job failing for retention policy with drop_created_before argument
  • #​9557 Clean up orphaned compression_chunk_size entries during the extension upgrade
  • #​9551 Fix resource leaks on error paths for during a continuous aggregate refresh
  • #​9563 Fix gapfill out-of-order bucket creation during DST shift
  • #​9571 Fix concurrent refreshes of continuous aggregates

Thanks


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added dependencies Dependency updates safe-automerge Safe dependency update eligible for auto-merge labels Apr 15, 2026
@renovate renovate Bot force-pushed the renovate/timescale-timescaledb-2.x branch from cbfd5c2 to 6c47cb4 Compare April 28, 2026 21:48
@renovate renovate Bot changed the title chore(deps): update dependency timescale/timescaledb to v2.26.3 chore(deps): update dependency timescale/timescaledb to v2.26.4 Apr 28, 2026
@renovate renovate Bot force-pushed the renovate/timescale-timescaledb-2.x branch from 6c47cb4 to 2f177fc Compare May 12, 2026 08:55
@renovate renovate Bot changed the title chore(deps): update dependency timescale/timescaledb to v2.26.4 chore(deps): update dependency timescale/timescaledb to v2.27.0 May 12, 2026
@renovate renovate Bot changed the title chore(deps): update dependency timescale/timescaledb to v2.27.0 chore(deps): update dependency timescale/timescaledb to v2.26.4 May 12, 2026
@renovate renovate Bot force-pushed the renovate/timescale-timescaledb-2.x branch 2 times, most recently from 0e4d60c to de0fb94 Compare May 12, 2026 19:23
@renovate renovate Bot changed the title chore(deps): update dependency timescale/timescaledb to v2.26.4 chore(deps): update dependency timescale/timescaledb to v2.27.0 May 12, 2026
@renovate renovate Bot force-pushed the renovate/timescale-timescaledb-2.x branch from de0fb94 to b2bedfd Compare May 19, 2026 14:41
@renovate renovate Bot changed the title chore(deps): update dependency timescale/timescaledb to v2.27.0 chore(deps): update dependency timescale/timescaledb to v2.27.1 May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency updates safe-automerge Safe dependency update eligible for auto-merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants