← Back to home
Comparison · Analytics

tern vs TimescaleDB

A side-by-side editorial comparison of tern and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.

tern vs TimescaleDB: at a glance

FeatureternTimescaleDB
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesclinical-trials, tables, r-package, pharmaversetime-series, postgresql, columnstore, query-optimization
Last editorial update4d ago1d ago
WebsiteVisit →Visit →

What is tern?

tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.

tern builds the clinical-trial tables, listings, and graphs layer on top of rtables — occurrence counts, survival summaries, ANCOVA, incidence rates, subgroup and biomarker tabulations. The visible work across the window is a systematic refactor: dozens of analysis functions rewritten to drop make_afun() and adopt a common analysis-function style driven by rtables' additional_fun_params. Feature additions ride along with it.

Read the full tern trajectory →

What is TimescaleDB?

TimescaleDB is paying down correctness debt in its columnstore query paths.

The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.

Read the full TimescaleDB trajectory →

tern vs TimescaleDB: editorial side-by-side

T
tern
ANALYTICS
0.0

tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.

◆ Current state

tern builds the clinical-trial tables, listings, and graphs layer on top of rtables — occurrence counts, survival summaries, ANCOVA, incidence rates, subgroup and biomarker tabulations. The visible work across the window is a systematic refactor: dozens of analysis functions rewritten to drop make_afun() and adopt a common analysis-function style driven by rtables' additional_fun_params. Feature additions ride along with it.

◆ Where it's heading

This is a multi-release architectural migration, not incremental polish. Each release converts another batch of functions, and the count is large — roughly two dozen in the most recent entry alone, after a comparable batch the release before. Alongside it, the denom parameter is being threaded through counting functions and g_lineplot is accumulating layout control, both patterns of standardising arguments that previously varied per function.

◆ Prediction

The refactor should continue until the make_afun() dependency is gone entirely, with the remaining tabulate_* and biomarker functions the likely next batch; the entries give no date for completion.

T
TimescaleDB
ANALYTICS
5.0

TimescaleDB is paying down correctness debt in its columnstore query paths.

◆ Current state

The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.

◆ Where it's heading

The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.

◆ Prediction

With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.

Alternatives to tern and TimescaleDB

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either tern or TimescaleDB.

See all tern alternatives → · See all TimescaleDB alternatives →

Recent activity from tern and TimescaleDB

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoTimescaleDB2.29.2: SkipScan and sparse-index correctness fixes
  2. 15d agoTimescaleDB2.29.1: security fixes plus compression bugfixes
  3. 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
  4. 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
  5. 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
  6. 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
  7. 1y agoternTwo dozen more analysis functions drop make_afun()
  8. 1y agoterndenom threading, custom statistics, and compare_vars merged in
  9. 1y agoternRisk-difference columns for subgroup tables
  10. 2y agoterng_lineplot gains faceting and axis controls

Frequently asked questions

What is the difference between tern and TimescaleDB?

They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is tern better than TimescaleDB?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to tern?

Top tern alternatives in Analytics are ranked by recent ship velocity. Browse the "tern alternatives" section above for the current picks, or visit /alternatives/tern for the full list with editorial commentary on each.

What are the best alternatives to TimescaleDB?

Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.