LoginSign Up
← Back to all sparks
T

TimescaleDB

ANALYTICS
Velocity5.0

Time-series database built on PostgreSQL

www.timescale.com ↗

TimescaleDB 2.32 turns on its new integer compressor and drops superuser needs.

time-seriescolumnstorecompressionpostgressecurity
◆Current state
TimescaleDB ships on a steady cadence where most releases are columnstore, SkipScan and continuous aggregate fixes. 2.31.0 vectorized UPDATE and DELETE on compressed data and previewed an Adaptive Integer Compressor. 2.32.0 turns that compressor on by default, speeds continuous aggregate refreshes, and arrives with a larger than usual batch of security fixes: background workers, the scheduler and telemetry now run as the database owner rather than as superuser.
◆Where it's heading
Feature releases keep cutting the cost of running large hypertables, while 2.32 adds a second thread: running safely without superuser rights. That matters most for managed and multi-tenant Postgres setups where superuser is not available.
◆Prediction
Expect quick 2.32.x patches for the new compressor and the owner-based worker model, as happened after 2.30's planner change; the release already points users to 2.32.1 before upgrading Postgres.

◆Recent moves

  1. 1d ago

    2.32.0: integer compression on by default, owner-run workers

    Adaptive Integer Compression moves from preview to default, continuous aggregate refreshes update their watermark once per batch, and database owners can manage background workers without superuser. It follows 2.31's compression preview and comes with a security batch the team asks everyone to install soon.

    View source ↗
  2. 24d ago

    2.31.0: faster columnstore DML, adaptive integer compression preview

    2.31.0 extends vectorization to UPDATE and DELETE on the columnstore (up to 6.5x on some grouped queries), adds move_to_columnstore() without blocking concurrent writes, and previews an opt-in integer compressor slated to become default in 2.32. It continues the push to make compressed hypertables writable at speed, with two debug-only GUC renames as breaking changes.

    View source ↗
  3. 1mo ago

    2.30.2: chunk-merge crash fixes and renamed cagg refresh options

    A patch release fixing crashes in chunk merges and CREATE TABLE AS on compressed hypertables, plus orphaned compressed chunks after DROP SCHEMA CASCADE. The rename of the granular refresh options to cagg_granular_refresh_* is the one change users may need to act on.

    View source ↗
  4. 1mo ago

    2.30.1: fixes duplicate rows from the new DeferredChunkAppend

    Follow-up fixes for 2.30.0's DeferredChunkAppend, which returned duplicate rows and failed casts under generic plans. This is the expected cleanup after a planner change like that one.

    View source ↗
  5. 2mo ago

    2.30.0: last-point LIMIT queries no longer scale with chunk count

    DeferredChunkAppend defers chunk expansion until execution, so a last-point LIMIT query found in the newest chunk runs in roughly constant time instead of scaling with the chunk count. It continues the recency-query work from 2.28 and 2.29 and has the largest effect on long-retention hypertables.

    View source ↗
  6. 2mo ago

    2.29.2: SkipScan and sparse-index wrong-result fixes

    This patch fixes wrong results in SkipScan and sparse-index pushdown on compressed data, including COUNT(DISTINCT) dropping uncompressed rows. It is correctness work on the optimizations the recent minors introduced.

    View source ↗