← Back to home
Comparison · DevOps

pgBackRest vs rerddap

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

pgBackRest vs rerddap: at a glance

FeaturepgBackRestrerddap
SectorDevOpsDevOps
Velocity score5.00.0
Sparks · 30d00
Top themespostgresql, backup, object storage, least privilegeoceanographic-data, r-package, api-client, parquet
Last editorial update23h ago3d ago
WebsiteVisit →Visit →

What is pgBackRest?

pgBackRest tracks PostgreSQL 19 beta by beta, patching the hangs it finds along the way.

pgBackRest is in the tail of the 2.59 cycle, which brought PostgreSQL 19 support and restricted every command except restore from running as root. The 2.59.1 patch keeps step with PostgreSQL 19beta3 and clears three defects, including a hang that occurred whenever the chunk buffer was smaller than the input buffer. Release cadence remains a few feature releases a year with patches slotted between them.

Read the full pgBackRest trajectory →

What is rerddap?

An ERDDAP client steadily lowering the cost of pulling large oceanographic extracts

rerddap fetches gridded and tabular data from ERDDAP servers into R. The recent releases follow one practical thread — making large extracts cheaper to move — alongside routine robustness work on error messages and failure modes. 1.3.0 brings parquet output to `griddap()` and adds a function that estimates a download's size before the request is made.

Read the full rerddap trajectory →

pgBackRest vs rerddap: editorial side-by-side

P5.0

pgBackRest tracks PostgreSQL 19 beta by beta, patching the hangs it finds along the way.

◆ Current state

pgBackRest is in the tail of the 2.59 cycle, which brought PostgreSQL 19 support and restricted every command except restore from running as root. The 2.59.1 patch keeps step with PostgreSQL 19beta3 and clears three defects, including a hang that occurred whenever the chunk buffer was smaller than the input buffer. Release cadence remains a few feature releases a year with patches slotted between them.

◆ Where it's heading

Two currents continue. Support for the next PostgreSQL major arrives experimentally a full release before it is needed — 18 in 2.55.0, 19 in 2.59.0, and now tracking 19's betas point by point — so the backup tool is ready before the database ships. The second is a move away from ambient privilege and toward cloud-native identity: managed identities and pod identity in place of stored keys, and the root restriction narrowing what a compromised invocation can reach. The 2.59.1 fixes are the ordinary cost of that pace, including a packaging fault in the GitHub source archives.

◆ Prediction

Expect the beta-tracking patches to continue through PostgreSQL 19's release cycle, with the next feature release arriving after 19 goes final rather than before it.

R
rerddap
DEVOPS
0.0

An ERDDAP client steadily lowering the cost of pulling large oceanographic extracts

◆ Current state

rerddap fetches gridded and tabular data from ERDDAP servers into R. The recent releases follow one practical thread — making large extracts cheaper to move — alongside routine robustness work on error messages and failure modes. 1.3.0 brings parquet output to `griddap()` and adds a function that estimates a download's size before the request is made.

◆ Where it's heading

Parquet support has propagated across the package one function at a time: introduced for `tabledap()` in 1.2.0 where the maintainer reports up to 90% smaller files for large extracts, patched in 1.2.3, and extended to `griddap()` in 1.3.0. The size-estimation function added alongside it addresses the same problem from the other end, letting a user find out what a request will cost before committing to it. Around this, the package has absorbed the usual CRAN-driven hardening, notably making all external resource requests fail gracefully.

◆ Prediction

Expect the remaining data-access paths to converge on the same parquet-plus-pre-flight-estimate pattern, since that is how the last three feature releases have each extended it. The entries do not indicate work beyond data retrieval.

Alternatives to pgBackRest and rerddap

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 rerddap.

See all pgBackRest alternatives → · See all rerddap alternatives →

Recent activity from pgBackRest and rerddap

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

  1. 2d agopgBackRestv2.59.1: PostgreSQL 19beta3 Support
  2. 1mo agopgBackRestv2.59.0: PostgreSQL 19 Support
  3. 1mo agorerddapParquet output for griddap and pre-request size estimates
  4. 5mo agorerddapFix for parquet output in tabledap
  5. 7mo agorerddapInteractive plotting docs and clearer error messages
  6. 7mo agopgBackRestv2.58.0: Object Storage Improvements
  7. 10mo agopgBackRestv2.57.0: Suppress Repository Symlinks
  8. 1y agopgBackRestv2.55.1: Bug Fixes
  9. 1y agopgBackRestv2.56.0: Progress Info Improvements
  10. 1y agorerddapGraceful failure when ERDDAP servers are unavailable
  11. 1y agorerddapParquet downloads and units attributes for tabledap
  12. 2y agorerddaptabledap returns types matching the server dds

Frequently asked questions

What is the difference between pgBackRest and rerddap?

They serve adjacent needs but don't currently overlap on shipped themes. pgBackRest 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 pgBackRest better than rerddap?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. pgBackRest 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 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 rerddap?

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