10 ms·
Pgbackrest is no longer being maintained
- philipallstar 5mo agoSorry to hear this. Well done for maintaining a successful project for so long.
- timwis 5mo agoReally 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.
- oulipo2 5mo agoWaiting 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
- absynth 5mo agoThe backups will then be hyper-optimized from three hours down to 5 minutes using devnull compression technologies. Its super effective!
- duskdozer 5mo agoWhy even waste all this time and money on backups in the first place? Just don't make mistakes.
- theandrewbailey 5mo agoOnly for their AI to delete the production database and all the backups, and be forced to write an apology. https://news.ycombinator.com/item?id=47911524 https://news.ycombinator.com/item?id=47911524
- dzonga 5mo agoThe A.I will probably steal the code and make it an unmaintainable mess that deletes backups when someone tries to restore
- evertheylen 5mo agoAh, sad to read this. Does anyone know of good alternatives?
- DeathArrow 5mo agoPostgres has built-in backups starting with version 18.
- evertheylen 5mo agoFrom what I can find Postgres 17 [1] introduced incremental backups to pg_basebackup, refined in 18, but nowhere near the full featureset of pgBackRest. Is that what you meant? Having builtin incremental replication to a S3-compatible storage would be great. [1]: https://www.postgresql.org/docs/release/17.0/#:~:text=pg%5Fbasebackup%20now%20supports%20incremental%20backup https://www.postgresql.org/docs/release/17.0/#:~:text=pg%5Fb...
- whateveracct 5mo agodoesn't it still work?
- evertheylen 5mo agoYes! But I'm assuming it will prevent me from upgrading to Postgres 19 in the future.
- whateveracct 5mo agoI'm not familiar with the internals, but is backing up that coupled to Postgres version? That feels so brittle to me.
- indigo945 5mo agoYou can of course take a SQL dump that is version-independent, but if you're serious about creating backups, you want to take backups of the actual on-disk format of the WAL, because that's more efficient and also the only practical way to get point-in-time recovery. (For the efficiency, you could alternatively also take ZFS snapshots, which will work independently of the Postgres version, but those also don't give you PITR.) The WAL format is a Postgres implementation detail and therefore tools wanting to read and write it need maintenance whenever the format changes (which can happen on major version releases).
- hleszek 5mo agoWhy 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.
- c0balt 5mo agoIt is reasonable to ask for a follow-up project/fork to take a different name. Naming your project, e. G., pgbackrest-ng, does not sound too onerous of a requirement and clearly communicates to users that maintainers have changed (see also paperless ng/ngx as good examples of such a change). Finding a successor is also not easy nor cheap (in regards to time).
- xnorswap 5mo agoYou'll also find plenty of potential malware injectors too, and who would want the responsibility of trying to vet a successor and have to work out the difference?
- jeswin 5mo agoThere's no way to know if a new maintainer will live up to whatever standards they've kept to date. Archiving should be the default decision, unless there's formal and elaborate handover.
- dschuessler 5mo agoBecause you will attract people who will want to take advantage of the trust these 3.8k stars signal to some people, for example, by means of supply chain attacks.
- leoc 5mo agoThe Apache Foundation used to help with this sort of governance problem didn't it? Thugh maybe pgbackrest isn't quite big and official enough to be the kind of software which Apache takes on, and one certainly hears (increasing?) grumbles about Apache's stewardship.
- hombre_fatal 5mo ago
- colesantiago 5mo ago> 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.
- wg0 5mo agoVery simple. Name it to pgbackrest-AI and add the line: "AI driven backups with smartest world class models optimizing every byte stored via deep AI analysis." With that added, a million dollars is just chimp change. YC alone would be adding them to all the seasons multiple times over summer, winter and monsoon etc.
- voidmain0001 5mo agoEven with sponsorship, it's not always appreciated such as Vercel backing Svelte, Vue, etc. https://www.reddit.com/r/reactjs/comments/1g4lu5p/am_i_seeing_things_or_vercel_basically_owns/ https://www.reddit.com/r/reactjs/comments/1g4lu5p/am_i_seein...
- colesantiago 5mo agoThe responses in there are dumb and childish. I doubt that they have sponsored an OSS project or made it sustainable.
- nijave 5mo agoPostgres doesn't compete with Snowflake. Snowflake recently announced a Postgres DBaaS offering that integrates with Snowflake (actually has competitive pricing with AWS RDS Postgres) They're two non competing verticals. It's a shame Snowflake decided to shrink Crunchy Data's community presence.
- fabian2k 5mo agoI 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.
- drcongo 5mo agoThis is exactly what I was setting it up to do this morning. My research came down to this and WAL-G for the same reasons, and I picked pgBackRest over WAL-G because the documentation was clearer.
- bobkb 5mo agoSo sad. We have been using this amazing project extensively
- hauxir 5mo agobeen using databasus(https://github.com/databasus/databasus https://github.com/databasus/databasus) works pretty well so far.
- cpursley 5mo agoSame, was really easy to set up.
- zigzag312 5mo agoThis project looks nice, albeit a bit young for a backup tool. Did you encounter any issues or limitations?
- arend321 5mo agoI'm also using this project. Easy to configure and operate. I am feeling a slight unease using such a recent project for things as important as the database. But the polished interface combined with the easy docker deployment made me use it anyway. Restores need some permission tuning on PostgreSQL but otherwise happy. They are very proud of their github star acquisition curve [0], the "blessing" by Anthropic [1] But I have yet to verify the Anthropic claim. [0] https://www.reddit.com/r/selfhosted/comments/1q94uu9/selfhosted_postgresql_backup_tool_with_ui/ https://www.reddit.com/r/selfhosted/comments/1q94uu9/selfhos... [1] https://www.reddit.com/r/ClaudeAI/comments/1rklvr7/anthropic_supported_open_source_postgresql_backup/ https://www.reddit.com/r/ClaudeAI/comments/1rklvr7/anthropic...
- rostislav_dugin 5mo agoI am proud of course, because a huge amount of time and effort invested in this :) However, it's really sad that pgBackRest has been closed, because I was led by pgBackRest in some sense when started Databasus
- Nelkins 5mo agoWow, 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/wal-g/wal-g https://github.com/EnterpriseDB/barman https://github.com/EnterpriseDB/barman
- noosphr 5mo ago>Wow, this is pretty surprising, I was under the impression that this is the leading PG backup/recovery tool. https://xkcd.com/2347/ https://xkcd.com/2347/
- andruby 5mo agoWe'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.
- fabian2k 5mo agoAre 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.
- andruby 5mo agoWAL-G's PITR backups are insurance against data loss through erroneous data manipulations (eg: accidental DELETE/DROP/UPDATE). WAL-G's streaming approach (using pg_receivewal or similar) sends WAL records to backup storage continuously as they're generated, rather than waiting for a full segment to complete. On top of that, for availability (and minimizing deadtime), we have 2 replicas using streaming replication. If the lead PG crashes, one of the replicas is promoted to lead (and starts accepting writes), and we "only" lose the writes that haven't been sent over the streaming replication. You can fully eliminate that window of data loss with synchronous replication (vs the default asynchronous replication - which we use). The write slowdown (replica network round trip + 2nd write at replica) isn't worth it for us
- freakynit 5mo agoSo 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-guide https://github.com/freakynit/postgre-backup-and-restore-guid... Thanks to the author for all the time and effort he put into this project..
- 2ndorderthought 5mo agoI really wish projects like this didn't fall through the cracks and continued to be funded. The struggles of OSS are too real.
- freakynit 5mo agoTrue.. 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 is way worse.. where giant companies rip off the hardwork of open-source software maintainers without compsensating them adequately.
- topham 5mo agoSigh. 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.
- duskdozer 5mo agoMay 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.
- DeathArrow 5mo agoI have recently configured pgbackrest for our app. :(
- joshmn 5mo agoI 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.
- drcongo 5mo agoI can beat you on the timing - I'd never used pgBackRest before, but started setting it up on a project about 2 hours ago, by the time I'd finished the README had been updated.
- hosteur 5mo agodatabasus does not do PITR.
- zigzag312 5mo agoIs that info up-to-date? Their readme states: **Backup types** - **Logical** — Native dump of the database in its engine-specific binary format. Compressed and streamed directly to storage with no intermediate files - **Physical** — File-level copy of the entire database cluster. Faster backup and restore for large datasets compared to logical dumps - **Incremental** — Physical base backup combined with continuous WAL segment archiving. **Enables Point-in-time recovery (PITR)** — restore to any second between backups. Designed for disaster recovery and near-zero data loss requirements EDIT: It seem PITR has been added this March (for PostgreSQL) https://github.com/databasus/databasus/issues/411 https://github.com/databasus/databasus/issues/411
- rostislav_dugin 5mo agoDatabasus does support PITR
- sgarland 5mo agoI've used barman on somewhat large-ish DBs (30+ TB), and had no complaints with it. I am a DBRE, if that holds any weight.
- dijit 5mo agoWow! 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-backup-server/ https://blog.dijit.sh/that-time-my-manager-spend-1m-on-a-bac...) This is really a major loss. :(
- nailer 5mo agoMentioned this on X but CockroachDB should sponsor this - their audience is Postgres people and open source contributions can be great marketing.
- pjmlp 5mo agoPlenty of comments of "So sad I have been using this". How many actually contributed back to keep it going?
- LetMeLogin 5mo agoI am not sure why are you gatekeeping this? People can't comment now that they are sad because of what happened?
- pjmlp 5mo agoGatekeeping?!? 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.
- piva00 5mo agoThat 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.
- AndyNemmity 5mo agoThe reason for something to exist is not to be used. He was paid while doing it, and that pay stopped, and he kept doing it. Now he wishes to stop. The reason for something to exist is someone finds joy doing it. Especially when they are unpaid. The sadness should be focused on his inability to support himself with a tool that clearly a lot of companies, and people are using and gaining value for.
- piva00 5mo agoThe reason for a tool to exist is to be used, even if it's just by a singular person, other projects that aren't tools do definitely fit into the criteria "just for the joy of it" but a tool, by definition, has at least one usage, and building a tool gives someone joy from the tool being useful. The sadness doesn't need to be focused anywhere, you can feel sad for more than one thing at a time. People can be sad that a tool they think is great, have relied on, and has been important for their use case is going away while also be sad that such a great tool doesn't get enough support from companies. Both can be true, no need to control what people can or should feel.
- iconicBark 5mo agoI use pgbackrest for some databases in production, and it has been VERY good.
- feike 5mo agopgbackrest 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.
- j1elo 5mo agoOpen 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.
- spockz 5mo agoI wonder whether the author has considered taking the product to a paid level and what would be necessary for it. Obviously, all contributors have some form of copyright, which may or may not have been waived depending on whether there was an ACL in place and jurisdiction. So he would need to get permission from the copyright holders, maybe in exchange for a percentage of the profit.
- pasc1878 5mo agoANd that gets rather looked on here as the authors being deceitful and not really Open Source doing a bait and switch.
- tracker1 5mo agoI've been working on a software package I'm hoping to release in a few months... I'm really torn on either split FLOSS with commercial extensions, or just going fully private... I was planning on a pretty generous free tier, but hoping to make a bit on the side from commercial customers. It's a bit of a niche as it is, so that's going to be rough in any kind of pricing model, as a large part of that niche is either homebrew types and the other commercial industry that will likely require some more integrations and customization.
- freedomben 5mo ago> 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.
- Latty 5mo agoTo 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.
- freedomben 5mo agoI totally agree, that is a huge risk. But what if someone from the postgres team decided to step up and maintain it? I'm not saying that's likely, but it is possible for a very popular tool like this. With the way the project exited now, that would not at all be an option. Obviously if postgres themselves decided to do it, they wouldn't need the previous credibility so this isn't the best example
- _flux 5mo agoIf someone really wants to continue the name, they can of course ask the author; maybe they have a compelling case.
- leoc 5mo agoThe Apache Foundation used to step in in this kind of situation, didn't it? Thugh maybe pgbackrest isn't quite big and official enough to be the kind of software which Apache takes on, and one certainly hears (increasing?) grumbles about Apache's stewardship.
- thrownaway561 5mo agoi 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.
- alex_suzuki 5mo agoadding to that, lots of devs don’t want the hassle of running a software business
- dzonga 5mo agoprops to the author for such fine work. hopefully some of the big co's step up & pay a retainer to keep the author going.
- bdcravens 5mo ago"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.
- thinkingtoilet 5mo agoThis is the right attitude. All the "this is sad" comments make me want to ask, "How sad are you? Sad enough to donate?"
- spockz 5mo agoFor me the sad part about the story is that someone who clearly knows what they are doing wasn’t able to find a job that would have permitted him to continue working on the project and that there were insufficient sponsors from companies. Not the fact that he made the decision he made.
- manquer 5mo agoDatabase backup tools are used primarily in enterprise context. (In)Ability to donate is not a function of personal spending preferences A fair amount of people work here at orgs on here would absolutely be able to swing couple of hundred bucks per month in sponsorship or licensing or donations for a critical tool in their infra toolkit without lot of effort. Particularly so, with the rising frequency of AI deleted my prod posts.
- radimm 5mo agoThis 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!
- drcongo 5mo agoThat text is right there in the link, we don't need to read it twice.
- stronglikedan 5mo agoWhy did you read it twice if you didn't need to? Seems unnecessary. I only read it once and just ignored it on subsequent encounters.
- drcongo 5mo agoTrying to find what context was on LinkedIn but not in the posted link. Spoiler alert, there was none.
- aetherspawn 5mo agoIt 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.
- spockz 5mo agoAnd hopefully someone wants to stand up then. Not sure whether it needs to be a fork or that they can join as contributor on the repo.
- steveharing1 5mo agoI 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
- poopsmithe 5mo agoAnyone looking for an alternative can try UFO Backup aka pgbackweb https://github.com/eduardolat/pgbackweb https://github.com/eduardolat/pgbackweb
- WaitWaitWha 5mo agodo 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.
- loloquwowndueo 5mo ago*bear, not bare.
- WaitWaitWha 5mo agoNo. I meant bare. As in "... what if, expose/uncover [this topic] with me, what if, ..."
- loloquwowndueo 5mo agoHahaha this made my day thanks!
- maherbeg 5mo agopgbackrest 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.
- dcchambers 5mo agoWe'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.
- dotBen 5mo agoIt'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).
- Aeolun 5mo agoI don’t understand this? I donate plenty of tokens towards OSS. I guess it’s anthropic donating the tokens because they give me about $5k of API tokens for the $200 I pay them.
- nemomarx 5mo agoYou could also donate money to allow the devs to spend it on tokens, right?
- killingtime74 5mo agohttps://claude.com/contact-sales/claude-for-oss https://claude.com/contact-sales/claude-for-oss open source maintainers can get this. Chatgpt also has similar https://developers.openai.com/community/codex-for-oss https://developers.openai.com/community/codex-for-oss
- afgrant 5mo agoDoes Postgres no have online backup built in? All of the other major DBMSes do.
- zie 5mo agoSee the documentation: https://www.postgresql.org/docs/current/backup.html https://www.postgresql.org/docs/current/backup.html all of these various 3rd party backup tools use these things. Mostly it's QOL stuff that you get from a 3rd party tool. We use barman, very happily: https://pgbarman.org/ https://pgbarman.org/
- nijave 5mo agoHopefully barman has some longevity being under EDB assuming some hyperscaler doesn't gobble them up
- zie 5mo agoBarman has been around since 2011, released under the GPL. If it does get ruined by someone, I'll replace it in my stack or fork it for maintenance myself. I'm not very worried though. EDB has been in private equity(PE) hands since 2019 with out managing to ruin it so far. The ownership in PE hands seems to be pretty stable, so it doesn't look like the typical pump/dump mess you often see from crappy PE money.
- nijave 5mo agoPostgres is very "unix-y" in that everything is a separate tool. It has backup interfaces and commands but doesn't ship with a comprehensive backup management solution.
- immanuwell 5mo agothirteen 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
- Aeolun 5mo agoIs 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.
- hombre_fatal 5mo agoMotte: if you stop maintaining a project, it won’t become unusable in six months. Bailey: maintaining a popular project is not that much work. What?
- matkoniecz 5mo ago> Is it really that much effort to maintain something? yes see https://news.ycombinator.com/item?id=47921198 https://news.ycombinator.com/item?id=47921198 for start
- whateveracct 5mo agolol so a backup system was brittle enough that it needs a guy constantly working on it? which implies I need to constantly update?
- Aeolun 5mo agoYou quoted the original post I responded to back at me as an answer to my doubt?
- imrozim 5mo agoThis 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
- mmaunder 5mo agoMetrics 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.
- SupLockDef 5mo agoAnother 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/ https://blogs.gnome.org/chergert/author/chergert/ [2] https://github.com/nvim-treesitter/nvim-treesitter/discussions/8627 https://github.com/nvim-treesitter/nvim-treesitter/discussio... [3] https://discourse.gnome.org/t/stepping-down-as-libxml2-maintainer/31398/8 https://discourse.gnome.org/t/stepping-down-as-libxml2-maint...
- saadn92 5mo ago[flagged]
- elAhmo 5mo agoIt didn't go dark, and doesn't seem that critical in general. General idea still stands, but it is not like this just disappeared and backups will stop working.
- rowanG077 5mo agoWhy does sqlite not suffer from the same risk?
- Matl 5mo agoBecause it's a single file you can back up like any other?
- cornstalks 5mo agoSQLite doesn’t depend on donations. They have a consortium, sell licenses (it is open source but some companies like the explicit CYA), sell support contracts, sell an aviation-grade test harness, and sell extensions. Of course there is always the risk it goes out of business like any other company, but it’s not funded like your typical small open source project and doesn’t even allow open contributions (not necessarily a bad thing IMO but it’s just a totally different type of project).
- borplk 5mo agoI 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.
- alexpadula 5mo agowild isn't it
- ellieh 5mo agoI 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 :/
- artyom 5mo ago> know which projects are in desperate need of funding keyword: desperate... until the metric becomes the target, and stops being a good metric.
- michaelsun2026 5mo ago[dead]
- vanessafridman6 5mo ago[dead]
- Dana224 5mo ago[dead]
- Dana224 5mo ago[flagged]
- deleted 5mo ago[deleted]
- Sara_Nabih 5mo agoI 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/ https://pgmoneta.github.io/
- jimmypk 5mo ago[flagged]
- mohamedabdallah 5mo ago[dead]