immudb
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
Comparison · DevOps
pgBackRest vs QuestDB
A side-by-side editorial comparison of pgBackRest and QuestDB — release velocity, themes, recent moves, and the top alternatives to consider.
pgBackRest vs QuestDB: at a glance
What is pgBackRest?
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
2.59.0 in July added PostgreSQL 19 support and changed a long-standing default: only the restore command may run as root now, with anything else requiring an explicit allow-root. The same release ships a pregenerated distribution tarball so packagers no longer need the code-generation toolchain, and picks up an optional libsystemd dependency. Before it, 2.58.0 concentrated on object storage — HTTP support for S3, GCS and Azure, Azure managed identities, experimental S3 EKS pod identity, and configurable TLS cipher suites.
What is QuestDB?
QuestDB 10.0 collapses ingest and egress into one binary protocol, then aims at agent-run notebooks.
QuestDB just shipped 10.0, its first major version bump in the visible window, built around QWP — a binary columnar wire protocol that handles writes going in and streams Arrow back out through a single client. The release also carries live views in beta, notebooks driven by coding agents, and the storage groundwork that QuestDB Enterprise 4.0 builds cold storage on. Around the releases, the feed is mostly engineering deep-dives (HotSpot JIT internals, benchmark methodology), customer case studies in capital markets and fraud detection, and comparison guides.
pgBackRest vs QuestDB: editorial side-by-side
pgBackRest
2.5DEVOPS
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
◆ Current state
2.59.0 in July added PostgreSQL 19 support and changed a long-standing default: only the restore command may run as root now, with anything else requiring an explicit allow-root. The same release ships a pregenerated distribution tarball so packagers no longer need the code-generation toolchain, and picks up an optional libsystemd dependency. Before it, 2.58.0 concentrated on object storage — HTTP support for S3, GCS and Azure, Azure managed identities, experimental S3 EKS pod identity, and configurable TLS cipher suites.
◆ Where it's heading
Two currents run through this window. The first is keeping pace with PostgreSQL itself, where support arrives experimentally a release early — PostgreSQL 18 in 2.55.0, 19 in 2.59.0 — so the backup tool is ready before the database is. The second is a steady move toward cloud-native identity and away from ambient privilege: managed identities and pod identity replace stored keys, and the root restriction narrows what a compromised invocation can reach.
◆ Prediction
Given the pattern of adding experimental support one PostgreSQL cycle ahead and hardening defaults as the release lands, the next release is likely to promote PostgreSQL 19 support out of its initial state. The notes do not say whether allow-root will be deprecated further.
QuestDB
6.3DEVOPS
QuestDB 10.0 collapses ingest and egress into one binary protocol, then aims at agent-run notebooks.
◆ Current state
QuestDB just shipped 10.0, its first major version bump in the visible window, built around QWP — a binary columnar wire protocol that handles writes going in and streams Arrow back out through a single client. The release also carries live views in beta, notebooks driven by coding agents, and the storage groundwork that QuestDB Enterprise 4.0 builds cold storage on. Around the releases, the feed is mostly engineering deep-dives (HotSpot JIT internals, benchmark methodology), customer case studies in capital markets and fraud detection, and comparison guides.
◆ Where it's heading
The protocol work is the thread that matters. QuestDB has been positioning against InfluxDB Line Protocol on ingestion throughput for a while — the QWP post claims 33M rows/s on one machine at a million series, roughly 3.6x ILP over a network — and 10.0 turns that from a benchmark argument into the default path in and out. Folding Arrow egress into the same protocol points the database at the Python analytics stack directly rather than through a SQL driver, which the Polars and ConnectorX content has been rehearsing for months. The agent-driven notebooks and live views are earlier-stage, and the Enterprise line (storage policies, Parquet tiering, column-level GRANT) continues on its own track.
◆ Prediction
Expect QuestDB Enterprise 4.0 next, built on 10.0's storage work and leading with cold storage, plus client libraries catching up to QWP one language at a time. Live views and the agent notebooks look likeliest to move from beta on a later minor rather than in the next release.
Alternatives to pgBackRest and QuestDB
Other DevOps 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 pgBackRest or QuestDB.
Sonic
Sonic is shipping tokenizer control and a dependency diet, two tags at a time.
Postgres Operator
Zalando's Postgres Operator finally shipped v2 — and had to reissue it within a day.
NebulaGraph
A graph database spending its releases on query-language parity and traversal speed.
Manticore Search
Manticore tags a GitHub release per commit, so the real news is one entry in five.
Vitess
Two patch lines, every release published twice, and no feature news since v24.0.0.
See all pgBackRest alternatives → · See all QuestDB alternatives →
Recent activity from pgBackRest and QuestDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoQuestDBQuestDB 10.0: QWP, one binary streaming protocol for writes and Arrow reads ⚡
- 2d agoQuestDBIntroducing QuestDB's new binary ingestion protocol: QWP
- 18d agopgBackRestv2.59.0: PostgreSQL 19 Support
- 18d agoQuestDBTransaction Cost Analysis with QuestDB and Polars: VWAP, Slippage and Markout
- 21d agoQuestDBHDFC Bank uses QuestDB for mule account detection across all major 25+ banking channels
- 23d agoQuestDBThe Most Expensive Instruction Might Be… cmov
- 1mo agoQuestDBThe Best Time-Series Databases in 2026 (and How to Choose)
- 6mo agopgBackRestv2.58.0: Object Storage Improvements
- 9mo agopgBackRestv2.57.0: Suppress Repository Symlinks
- 1y agopgBackRestv2.55.1: Bug Fixes
- 1y agopgBackRestv2.56.0: Progress Info Improvements
- 1y agopgBackRestv2.55.0: Verification Improvements and PostgreSQL 18 Support
Frequently asked questions
What is the difference between pgBackRest and QuestDB?
They serve adjacent needs but don't currently overlap on shipped themes. QuestDB is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 pgBackRest better than QuestDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. QuestDB is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to pgBackRest?
Top pgBackRest alternatives in DevOps are ranked by recent ship velocity. Browse the "pgBackRest alternatives" section above for the current picks, or visit /alternatives/pgbackrest for the full list with editorial commentary on each.
What are the best alternatives to QuestDB?
Top QuestDB alternatives in DevOps are ranked by recent ship velocity. Browse the "QuestDB alternatives" section above for the current picks, or visit /alternatives/questdb for the full list with editorial commentary on each.