Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pgbackrest is no longer being maintained

github.com

Post reply on HN
Print view View original

51–60 of 245 posts

Re: Pgbackrest is no longer being maintained

#51

Post by piva00 »

pjmlp wrote: post #39
LetMeLogin wrote: post #35

Earlier quoted context omitted.

I am not sure why are you gatekeeping this? People can't comment now that they are sad because of what happened?

Gatekeeping?!? Those that paid , or did any kind of contributions upstream are entitled to be sad. Others should consider this is what happens to that lego piece in Nebraska, when no one contributes, and everyone uses it.

That is exactly gatekeeping, no? You are only entitled to feel sad if you contributed effort or financially, otherwise you aren't allowed to feel.

Why can't others that just used the tool feel sad? It is supposed to be used, it's the whole reason for it to exist; not everyone using it will have technical expertise or money to contribute to it, feeling sad about it when it solved issues for someone is a completely normal response.

Re: Pgbackrest is no longer being maintained

#52

Post by didgetmaster »

2ndorderthought wrote: post #30
freakynit wrote: post #23

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

I really wish projects like this didn't fall through the cracks and continued to be funded. The struggles of OSS are too real.

The project is being abandoned because the maintainer is tired of working for free. They said that they hoped someone would fork it, change the name, and pick up where it was left off.

Why would anyone do that? If the person who was most passionate about it for over a dozen years has given up because it was never worth the trouble; what fool would think things will be different going forward?

This is the curse of OSS.

Re: Pgbackrest is no longer being maintained

#53

Post by fabian2k »

andruby wrote: post #47
Nelkins wrote: post #22

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

We've been happy with WAL-E and now WAL-G (successor). The streaming PITR nature of these won over pgbackrest when we did the analysis ~9 years ago.

Are you using WAL archiving? As far as I understand, pgbackrest and Barman can also use direct streaming from the DB (same mechanism as replication), I didn't find any mention of this in the WAL-G documentation.

With WAL archiving you need to wait for a WAL segment to finish before it's backed up. With streaming backups the deadtime is minimized. At least that's as far as I understand this, I didn't get to try this out in practice yet.

Re: Pgbackrest is no longer being maintained

#54

Post by duskdozer »

topham wrote: post #45
freakynit wrote: post #34

Earlier quoted context omitted.

True.. I truly wish wish we had better open-source license and more open-source projects adopt it.. Tiered pricing license... tiering based upon annual company revenues... should start super low for small companies (free for individuals), and jump to thousands of dollars per year for 10+ milion revenue companies. I understand that this might not fully be in the spirit of open-source, but, what's happening currently i…

Sigh. Bane of my existence is any service which does this. My org theoretically makes hundreds of millions, unfortunately none of that money is ours. So I get forced into a procurement process for anything that costs more than (ridiculously small limit), and get stuck using the worst in class because it's cheaper.

May be inconvenient to you, but the point of licenses like that is that inconvenience to companies that aren't willing to pay for the work.

Re: Pgbackrest is no longer being maintained

#55

Post by freedomben »

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

Re: Pgbackrest is no longer being maintained

#57

Post by 2ndorderthought »

topham wrote: post #45
freakynit wrote: post #34

Earlier quoted context omitted.

True.. I truly wish wish we had better open-source license and more open-source projects adopt it.. Tiered pricing license... tiering based upon annual company revenues... should start super low for small companies (free for individuals), and jump to thousands of dollars per year for 10+ milion revenue companies. I understand that this might not fully be in the spirit of open-source, but, what's happening currently i…

Sigh. Bane of my existence is any service which does this. My org theoretically makes hundreds of millions, unfortunately none of that money is ours. So I get forced into a procurement process for anything that costs more than (ridiculously small limit), and get stuck using the worst in class because it's cheaper.

It would be great if github or someone did something to support licenses like this. So procurement was more like a cloud spend. Companies could put caps on the monthly spend for the projects they use. Organizations should be used to paying for products from individuals just like how they do from megacorporations.

Re: Pgbackrest is no longer being maintained

#58

Post by dzonga »

oulipo2 wrote: post #4

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

The A.I will probably steal the code and make it an unmaintainable mess that deletes backups when someone tries to restore

Re: Pgbackrest is no longer being maintained

#59

Post by Latty »

freedomben wrote: post #55

> 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…

To me it reads as being worried that someone malicious could step in and use the project's name to do harm. If you don't have someone within the project with trust built ready-to-go, establishing that trust enough to hand over the project is a big task.
Post reply on HN