TimescaleDB 2.27 Brings Bloom Filter Pruning to Writes, but EXPLAIN Counters Can Mislead
TimescaleDB 2.27, released May 12, 2026, extends bloom-filter batch pruning to write operations, allowing UPDATE, DELETE, and UPSERT queries on compressed columnstore data to skip irrelevant batches without decompressing them. The feature can deliver up to 160x speedups for selective UPDATE and DELETE operations, and over 2x improvements for UPSERT. While the optimization is automatic, users must inspect new EXPLAIN (ANALYZE) counters to confirm it is actually firing on their workload. A key source of confusion is that the UPDATE/DELETE path and the UPSERT path use different counter names for the same underlying metrics, with no reconciliation in the official documentation. Developers upgrading to 2.27 are also warned that two undocumented behavioral changes in the release can silently break existing queries if not accounted for.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in