← Back to home
Comparison · Analytics

MVMR vs TimescaleDB

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

MVMR vs TimescaleDB: at a glance

FeatureMVMRTimescaleDB
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesmendelian randomization, r, causal inference, geneticstime-series, postgresql, columnstore, query-optimization
Last editorial update3d ago1d ago
WebsiteVisit →Visit →

What is MVMR?

MVMR spent 2026 discovering its own estimators had been returning the wrong numbers

MVMR implements multivariable Mendelian randomization — conditional instrument strength, pleiotropy tests and heterogeneity-robust effect estimation from GWAS summary data. The package has been releasing steadily through 2026, and the substantive releases are all corrections rather than features. Two core routines were found to be computing the wrong quantity outright: qhet_mvmr() built weights from the minimised objective value instead of the minimiser, and strhet_mvmr() never minimised the Q-statistic at all.

Read the full MVMR 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 →

MVMR vs TimescaleDB: editorial side-by-side

M
MVMR
ANALYTICS
0.0

MVMR spent 2026 discovering its own estimators had been returning the wrong numbers

◆ Current state

MVMR implements multivariable Mendelian randomization — conditional instrument strength, pleiotropy tests and heterogeneity-robust effect estimation from GWAS summary data. The package has been releasing steadily through 2026, and the substantive releases are all corrections rather than features. Two core routines were found to be computing the wrong quantity outright: qhet_mvmr() built weights from the minimised objective value instead of the minimiser, and strhet_mvmr() never minimised the Q-statistic at all.

◆ Where it's heading

This is a sustained audit, not a maintenance drift. Each release since February has fixed a specific analytical defect — omitted intercepts in the exposure-on-genotype regressions, a division by zero when a gencov list held exactly two variants, covariance matrices computed wrongly for matrix inputs, a spurious covariance warning — and several explicitly warn that reported values will differ from previous versions. The strhet_mvmr() rewrite to iteratively reweighted least squares also removes a combinatorial grid that could exhaust memory past three exposures, so the function is now usable as well as correct.

◆ Prediction

The corrections have been walking through the package function by function, and the ones with published fixes so far are the heterogeneity and covariance routines; the remaining untouched estimators are the natural next stop if the audit continues at this pace.

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 MVMR 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 MVMR or TimescaleDB.

See all MVMR alternatives → · See all TimescaleDB alternatives →

Recent activity from MVMR 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 agoMVMRMVMR rewrites strhet_mvmr() after finding it never minimised Q
  6. 1mo agoMVMRMVMR corrects qhet_mvmr() weights and three covariance bugs
  7. 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
  8. 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
  9. 3mo agoMVMRNew vignette on estimating phenotypic correlations
  10. 3mo agoMVMRMVMR 0.4.5
  11. 4mo agoMVMRMVMR 0.4.4
  12. 5mo agoMVMRMVMR restores intercepts omitted from snpcov_mvmr() regressions

Frequently asked questions

What is the difference between MVMR 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 MVMR 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 MVMR?

Top MVMR alternatives in Analytics are ranked by recent ship velocity. Browse the "MVMR alternatives" section above for the current picks, or visit /alternatives/mvmr 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.