Re: pgBackRest maintenance (was Re: Tablespace size in TB)

On Thu, May 14, 2026 at 07:54:30PM +0200, Josef Šimánek wrote:
> čt 14. 5. 2026 v 19:26 odesílatel Bruce Momjian <bruce(at)momjian(dot)us> napsal:
> >
> > On Sun, May 3, 2026 at 11:45:53PM -0700, Christophe Pettus wrote:
> > >
> > >
> > > > On May 3, 2026, at 22:55, Ilya Kosmodemiansky <ik(at)dataegret(dot)com>
> > > > wrote: Making a company-branded fork is the easiest (and wrong)
> > > > step. Planning how to pick up the pgBackRest project or create a
> > > > sustainable, community-driven fork that re-establishes at least the
> > > > same reputation requires longer preparation. We all need patience.
> > >
> > > Dave was quite clear that someone "picking up the pgBackRest project"
> > > was not on the table. I don't think that avenue is open.
> > >
> > > I would feel more sanguine about the idea that a new
> > > community-sported fork will emerge if there were an existence proof
> > > of it happening in the PostgreSQL community. I can't think of one.
> >
> > That happened with pgbouncer where development stopped and a new team
> > picked it up. I think Peter Eisentraut was involved. With pgbackrest,
> > I think a similar thing would need to happen, but with a new name.
>
> I think David is back and no fork is needed currently.
> https://github.com/pgbackrest/pgbackrest/commit/b93a2b8807adabec02ef33cca838e30f109c3eba

Well, the pgbackrest website doesn't say that:

https://pgbackrest.org/

I thought updating that would have been the first thing done if the
status changed.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.