immudb
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
Comparison · DevOps
Manticore Search vs pgBackRest
A side-by-side editorial comparison of Manticore Search and pgBackRest — release velocity, themes, recent moves, and the top alternatives to consider.
Manticore Search vs pgBackRest: at a glance
What is Manticore Search?
Manticore tags a GitHub release per commit, so the real news is one entry in five.
Only one item in the recent window is a release in the ordinary sense: 28.6.6, whose notes cover UUID document IDs for real-time tables — explicit or generated, with equality and IN filters and UUID-based REPLACE, UPDATE and DELETE — and an ordered, limited GROUP_CONCAT() that keeps the top N values per group. The rest are individual commits published as releases: a buddy dependency bump, a backup component bump, a fix restoring USER() parsing after authentication made USER a keyword, and a revert of UTF-8 table and field name support that had been merged by mistake.
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.
Manticore Search vs pgBackRest: editorial side-by-side
Manticore Search
5.0DEVOPS
Manticore tags a GitHub release per commit, so the real news is one entry in five.
◆ Current state
Only one item in the recent window is a release in the ordinary sense: 28.6.6, whose notes cover UUID document IDs for real-time tables — explicit or generated, with equality and IN filters and UUID-based REPLACE, UPDATE and DELETE — and an ordered, limited GROUP_CONCAT() that keeps the top N values per group. The rest are individual commits published as releases: a buddy dependency bump, a backup component bump, a fix restoring USER() parsing after authentication made USER a keyword, and a revert of UTF-8 table and field name support that had been merged by mistake.
◆ Where it's heading
The feature direction visible here is making Manticore behave more like the SQL engine users expect. UUID identifiers remove the requirement to mint your own document IDs, the GROUP_CONCAT extension closes a gap against MySQL semantics, and the USER() fix is repairing MySQL client compatibility that the new authentication support broke. The reverted UTF-8 identifier support belongs to the same effort and will presumably return deliberately.
◆ Prediction
UTF-8 table and field names were reverted as merged by mistake rather than rejected, so the clearest next step is that feature landing properly. The commit-per-release pattern means most upcoming entries will continue to be single fixes rather than release notes.
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.
Alternatives to Manticore Search and pgBackRest
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 Manticore Search or pgBackRest.
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.
Vitess
Two patch lines, every release published twice, and no feature news since v24.0.0.
Heroku
Runtime bumps fill the changelog; the managed Postgres line is where Heroku actually moves.
See all Manticore Search alternatives → · See all pgBackRest alternatives →
Recent activity from Manticore Search and pgBackRest
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoManticore SearchUTF-8 table and field name support reverted
- 1d agoManticore SearchBuddy component bumped from 4.2.0 to 4.3.0
- 7d agoManticore SearchUUID document IDs and ordered, limited GROUP_CONCAT()
- 8d agoManticore SearchUSER() parsing restored for MySQL client compatibility
- 9d agoManticore SearchBackup component bumped to 1.10.2
- 18d agopgBackRestv2.59.0: PostgreSQL 19 Support
- 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 Manticore Search and pgBackRest?
They serve adjacent needs but don't currently overlap on shipped themes. Manticore Search is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Manticore Search better than pgBackRest?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Manticore Search is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 Manticore Search?
Top Manticore Search alternatives in DevOps are ranked by recent ship velocity. Browse the "Manticore Search alternatives" section above for the current picks, or visit /alternatives/manticoresearch for the full list with editorial commentary on each.
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.