FRESH

Hacker News

Home

Pgbackrest is no longer being maintained

450 points by c0l0

by freakynit

2 subcomments

So sad to see this happening..
I had just last year prepared a detailed guide for reliable postgre backups to local volume as well as cloud storage, using pgBackRest, for my own projects.. pgBackRest have worked so well for me
https://github.com/freakynit/postgre-backup-and-restore-guid...
Thanks to the author for all the time and effort he put into this project..

by bdcravens

1 subcomments

"so sad to see this"
The source is still available. Maintaining your own copy and/or paying someone to do it is an option.
While you're at it, look at all the projects you depend on that you would similarly be sad about losing, and set up those donations today.

by dijit

0 subcomment

Wow! pgbackrest was definitely the premier backup solution for postgres when I last looked at the ecosystem properly.
It was the only solution that seemed to take restoring and validating as seriously as “taking a backup” which lead to an unfortunate situation with my employer. (details here: https://blog.dijit.sh/that-time-my-manager-spend-1m-on-a-bac...)
This is really a major loss. :(

by Nelkins

4 subcomments

Wow, this is pretty surprising, I was under the impression that this is the leading PG backup/recovery tool.
Anybody know how WAL-G and Barman compare?
https://github.com/wal-g/wal-g
https://github.com/EnterpriseDB/barman

by j1elo

2 subcomments

Open Source has worked fine here. The author doesn't find financial support for the work, so they just want to change winds and that's a perfectly fine path forward.
If this is really much more than a personal project "for fun, on my leisure time", and it became an actually serious product-level project that provides good value in commercial environments for people, there's clearly an opportunity for a for-profit company to step in and cover that niche. But that'd require that users became customers and actually departed from their money to pay for it :)
I guess most will switch instead to asking who's the next project maintainer to work on it, to whom the new bug reports and complaints can continue to be sent for free. But if there's money to be made by using a tool, there should be money paid for using it too. We "just" need to find the new generation of FOSS Financial Sustainability solutions that actually work! Donations don't make the cut.

by joshmn

7 subcomments

I have a moderately sized 2TB production database I have enjoyed using pgBackRest on, and was—this week—going to set it up on another 8TB database we have.
What's the next-closest thing? wal-g? barman? databasus? I only get to cosplay as a DBA.

by colesantiago

3 subcomments

> Since Crunchy Data was sold, I have been maintaining pgBackRest and looking for a position that would allow me to continue the work, but so far I have not been successful. Likewise, my efforts to secure sponsorship have also fallen far short of what I need to make the project viable.
So this was the problem, I thought Snowflake would pick up the sponsorship of this project but since it is a competing database it doesn't really make much sense.
I really wish many critical OSS projects get the sponsorship they need to continue.
Otherwise the software industry is in real trouble.
Forking it just passes the buck onto another maintainer with the same problem, this time without the original creator maintaining it.

by saadn92

3 subcomments

[flagged]

by feike

0 subcomment

pgbackrest is the most versatile piece of backup technology for PostgreSQL and in my experience the other products do not come close.
I am therefore quite sad to see this happen. It won't be easy to get feature parity with this great product.
I sincerely hope this is a reversible decision, or perhaps the postgres project could even absorb it into contrib.

by dcchambers

0 subcomment

We're going to see a lot of this over the next 1-2 years.
Software Engineers suddenly feel like they're fighting for their lives for employment, and time won't be "wasted" maintaining OSS for free.
We all need to eat.

by aetherspawn

1 subcomments

It still works, you can just keep using it.
I think that’s what the author would want. People to keep using it until it doesn’t work anymore.

by fabian2k

1 subcomments

I was about to set up Postgres backups with pgbackrest very soon. It looked like the most mature solution for my use case. What I was aiming for was continuous backups to an object storage provider, without a central DB server but the backup tool directly installed on the Postgres server.
I'll have to look at the alternatives again, I think that was mostly WAL-G and Barman. It looks like Barman doesn't support direct backup to object storage, unfortunately. And I find the WAL-G documentation very confusing. What I'm looking for is WAL streaming and object storage support, to minimize the amount of data that can be lost and so I don't have to run my own backup server.

by borplk

1 subcomments

I find it shocking (not really) that among the many BILLION dollar companies built on the back of Postgres there isn't enough sense to pay the salary of one dude to keep a project like this going forever.

by pjmlp

8 subcomments

Plenty of comments of "So sad I have been using this".
How many actually contributed back to keep it going?

by ellieh

1 subcomments

I wish it was easier to know which projects are in desperate need of funding because I love pgbackrest and totally would have donated here, and I suspect many others would have too :/

by hauxir

3 subcomments

been using databasus(https://github.com/databasus/databasus) works pretty well so far.

by dotBen

3 subcomments

It's funny how developer time is considered free, but tokens are not.
In other words when it comes to FOSS contribution, developer time can be donated but tokens can't - so as we move into agentic code era all FOSS development carries a cost unless it is purely done by hand (which more often it isn't).
Not saying this is what is going on here but it's presumably a factor if the author was looking for an employer to sponsor development with his labor (and tokens).

by oulipo2

4 subcomments

Waiting for all the C-level execs saying that "anyway this is not needed, we're going to vibe-code a solution to our production database backups" lol

by Sara_Nabih

0 subcomment

I think many people might be overlooking pgmoneta, it’s a powerful alternative and one of the most active backup projects in Google Summer of Code each year.
Highly recommended. Definitely worth taking a look: https://pgmoneta.github.io/

by evertheylen

2 subcomments

Ah, sad to read this. Does anyone know of good alternatives?

by imrozim

1 subcomments

This is scary as a solo dev who builts on postgresql. You pick a tool trust it, build around it, one day it stops. Oss sustainability is a real problem

by dzonga

0 subcomment

props to the author for such fine work.
hopefully some of the big co's step up & pay a retainer to keep the author going.

by timwis

0 subcomment

Really sad to see this. I had only recently learnt about this project, and was really impressed by it. I was planning to set it up this weekend (via autobase). I've also been under the impression that it's likely to be what powers the backups in RDS, Cloud SQL, etc., but I may have misunderstood.

by poopsmithe

0 subcomment

Anyone looking for an alternative can try UFO Backup aka pgbackweb https://github.com/eduardolat/pgbackweb

by maherbeg

0 subcomment

pgbackrest is awesome, truly. Thank you so much for the work you've put into this project over the years, and I'm sad the crunchy data acquisition couldn't keep the project alive.

by steveharing1

0 subcomment

I won't say He should be working on it no matter what but I believe its a very good project and I think as always community forks will be the only option when it won't work in future

0 subcomment

by nailer

0 subcomment

Mentioned this on X but CockroachDB should sponsor this - their audience is Postgres people and open source contributions can be great marketing.

by thrownaway561

1 subcomments

i wish the guy could have made a paid version so he could have continued it. Unfortunately, most people do not want to financially contribute to open source and especially when that open source project becomes a paid product.

by afgrant

2 subcomments

Does Postgres no have online backup built in? All of the other major DBMSes do.

by philipallstar

0 subcomment

Sorry to hear this. Well done for maintaining a successful project for so long.

by iconicBark

0 subcomment

I use pgbackrest for some databases in production, and it has been VERY good.

by immanuwell

0 subcomment

thirteen years of blood, sweat, and late nights shipped into the void - respect to David Steele for keeping it real and pulling the plug clean rather than letting it rot in maintenance burden

by bobkb

0 subcomment

So sad. We have been using this amazing project extensively

by SupLockDef

0 subcomment

Another one bites the dust...
Is it me ore I am seeing more and more projects being unmaintained due to financial and/or mental fatigue?
[1] https://blogs.gnome.org/chergert/author/chergert/
[2] https://github.com/nvim-treesitter/nvim-treesitter/discussio...
[3] https://discourse.gnome.org/t/stepping-down-as-libxml2-maint...

by DeathArrow

0 subcomment

I have recently configured pgbackrest for our app. :(

by radimm

4 subcomments

This is the message the author posted on LinkedIn:
After a lot of thought, I have decided to stop working on pgBackRest. I did not come to this decision lightly. pgBackRest has been my passion project for the last thirteen years, and I was fortunate to have corporate sponsorship for much of this time, but there were also many late nights and weekends as I worked to make pgBackRest the project it is today, aided by numerous contributors. Every open-source developer knows exactly what I mean and how much of your life gets devoted to a special project.
Since Crunchy Data was sold, I have been maintaining pgBackRest and looking for a position that would allow me to continue the work, but so far I have not been successful. Likewise, my efforts to secure sponsorship have also fallen far short of what I need to make the project viable.
Like everyone else, I need to make a living, and the range of pgBackRest-related roles is very limited. I can now consider a wider variety of opportunities, but those will not leave me time to work on pgBackRest, which requires a fair amount of time for maintenance, bug fixes, PR reviews, answering issues, etc. That does not even include time to write new features, which is what I really love to do. Rather than do the work poorly and/or sporadically, I think it makes more sense to have a hard stop.
I will post a notice of obsolescence and archive the repository. I imagine at some point pgBackRest will be forked, but that will be a new project with new maintainers, and they will need to build trust the same way we did.
Again, many thanks to all the pgBackRest contributors over the years. It was a pleasure working with you!

by WaitWaitWha

1 subcomments

do not yell at me, but... this is where genAI may be useful.
what if, bare with me, what if, after a certain amount of time, a certain amount of "requests", a code library can be given to a genAI to maintain; no improvements, no extra features, just bug fixes? This could continue until either someone picks it up, or the open source solution becomes irrelevant, not enough "requests".
Yes, lots of details to work out.

by mohamedabdallah

0 subcomment

[dead]

by jimmypk

0 subcomment

[dead]

by vanessafridman6

0 subcomment

[dead]

by michaelsun2026

0 subcomment

[dead]

by Dana224

0 subcomment

[dead]

by Dana224

0 subcomment

[flagged]

by hleszek

11 subcomments

Why not try to find a successor instead of archiving the repo and forbidding the use of the name? I'm sure with a 3.8k stars repo you'll find competent people willing to continue the work.

by mmaunder

0 subcomment

Metrics would help others who may want to rescue the project consider the options. Eg user base would make it clear if there’s an immediate opportunity to work with the author to launch a paid backup service around the project, funding continued work on it.

by freedomben

6 subcomments

> TL;DR: pgBackRest is no longer being maintained. If you fork pgBackRest, please select a new name for your project.
> I imagine at some point pgBackRest will be forked, but that will be a new project with new maintainers, and they will need to build trust the same way we did.
I completely understand having to back out of maintenance on an OSS project, but why also slam the door closed on someone taking over? There may be someone very qualified willing to step up, and that could give your existing users continuity.
This feels analgous to deciding to stop maintaining a community garden, but rather than let your neighbor step up, you decide to salt the ground so it can never grow there again, telling your neighbors "you can pull up my plants and move them, but you can't use all the ground and roots that are already there." It just feels bitter.

by Aeolun

2 subcomments

Is it really that much effort to maintain something? I’ll admit I haven’t the foggiest, my most maintained thing having like 200 stars or something, but if I leave it alone for half a year it doesn’t suddenly combust into flame.