compare
pgBackRest vs WAL-G
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | pgBackRest | WAL-G |
|---|---|---|
| Language | C | Go |
| Licence | Other | Other |
| Stars | 4.4k | 4.3k |
| Latest | release/2.60.0 | v3.0.9 |
| Last push | 2026-10-18 | 2026-10-18 |
| Release cadence | about 21 days between releases | about 211 days between releases |
| Active contributors | 8 commit authors on the default branch in the last 90 days | 31 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
WAL-G replaces pgBackRest. Alternatives to pgBackRest →
PartialPushes base backups and WAL to object storage, and also handles MySQL and other databases.
Both replace Amazon RDS. Alternatives to Amazon RDS →
PartialpgBackRestPoint-in-time recovery for self-hosted PostgreSQL, like RDS automated backups.
PartialWAL-GPoint-in-time recovery to S3-compatible storage for self-hosted databases.
pgBackRest
- release/2.60.02026-10-18v2.60.0: Page Checksum Errors and Object Store Prefetch
- release/2.59.32026-10-04v2.59.3: Weak Encryption Subkey Bug
- release/2.59.22026-09-27v2.59.2: PostgreSQL 19beta4 Support
- release/2.59.12026-08-17v2.59.1: PostgreSQL 19beta3 Support
- release/2.59.02026-07-20v2.59.0: PostgreSQL 19 Support
WAL-G
- v3.0.92026-08-20🛠 Centralized GOEXPERIMENT=jsonv2 management
- v3.0.82026-01-21Infrastructure & CI
- v3.0.72025-04-13From Greenplum's perspective, the following updates are beneficial: Commit 92e3995 introduces a --force-delete flag to…
- v3.0.62025-04-10pre-release
- v3.0.52025-01-10First stable release in 2025. Major features of this stable release are:
pgBackRest
unsigned The latest release, release/2.60.0, carries no signature GitHub could verify.
Loading the security report
WAL-G
✓ signed The latest release, v3.0.9, carries a signature GitHub verified.
Loading the security report