3 ms·
This is a fantastic project that a lot of self-hosters using PostgreSQL use. Specially with pgBackRest archived by the owner on Apr 27, 2026, this is likely the
by subhobroto 5mo ago
This is a fantastic project that a lot of self-hosters using PostgreSQL use. Specially with pgBackRest archived by the owner on Apr 27, 2026, this is likely the leading option that has been around the block for a while.
Anyone here had considered Barman in the past, used it for a while and went to pgBackRest? Are you revisiting that decision now?
- hans_castorp 5mo agoA side note on pgBackRest: PGX created a fork and announced to maintain it under the name pgxbackup: https://thebuild.com/blog/2026/05/01/pgxbackup-continuity-support-for-pgbackrest/ https://thebuild.com/blog/2026/05/01/pgxbackup-continuity-su...
- tee-es-gee 5mo agoIt looks like pgBackRest will likely continue, multiple companies are stepping up with sponsorships. Mentioning this just in case anyone is making plans to move away, it's probably worth waiting a bit for things to settle.
- zigzag312 5mo agoOne interesting thing about Barman is that it just uses PG's own backup utilities. It doesn't implement custom parsers and things like that. So, there's less maintenance work needed for Barman when PostgreSQL changes data-file internals. Tradeoff is that there's less custom optimization than pgBackRest/pg_probackup/WAL-G-local. Databasus seems to be taking somewhat similar approach to Barman, but (at this time) does not appear to use pg_receivewal, which makes it less efficient than Barman. For PG v17+, Barman seems to be the most efficient backup solution based on PG native tools, that is able to do low-RPO or even zero-RPO (if configured as a synchronous receiver).