public inbox for pgsql-general@postgresql.org
help / color / mirror / Atom feedFrom: Bruce Momjian <bruce@momjian.us>
To: Josef Šimánek <josef.simanek@gmail.com>
Cc: Christophe Pettus <xof@thebuild.com>
Cc: pgsql-general@lists.postgresql.org
Cc: Peter Eisentraut <peter@eisentraut.org>
Subject: Re: pgBackRest maintenance (was Re: Tablespace size in TB)
Date: Thu, 14 May 2026 15:56:38 -0400
Message-ID: <agYo9iveYcCHeKGt@momjian.us> (raw)
In-Reply-To: <CAFp7QwpDdGzhFaodOgoZJWsL9nU6+fbdVTJu0C_NvSyusnBtnQ@mail.gmail.com>
References: <81DB47B9-3244-41BA-980D-66AC371C8CA6@gmail.com>
<3166829D-694D-4A44-B7F5-A7D454EB77DD@gmail.com>
<CAG95seU1wFpHMLvLR+C1H9BDOK2jh_8RFxY3mmchtWUgMNu+ag@mail.gmail.com>
<DEBB18A6-E034-4222-B89A-99F3EB6EAF87@thebuild.com>
<agYF1Q6IVWwca0mH@momjian.us>
<CAFp7QwpDdGzhFaodOgoZJWsL9nU6+fbdVTJu0C_NvSyusnBtnQ@mail.gmail.com>
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@momjian.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@dataegret.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@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: bruce@momjian.us, josef.simanek@gmail.com, xof@thebuild.com, pgsql-general@lists.postgresql.org, peter@eisentraut.org
Subject: Re: pgBackRest maintenance (was Re: Tablespace size in TB)
In-Reply-To: <agYo9iveYcCHeKGt@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox