public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Christophe Pettus <[email protected]>
Cc: [email protected]
Cc: Peter Eisentraut <[email protected]>
Subject: Re: pgBackRest maintenance (was Re: Tablespace size in TB)
Date: Thu, 14 May 2026 13:26:45 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<CAG95seU1wFpHMLvLR+C1H9BDOK2jh_8RFxY3mmchtWUgMNu+ag@mail.gmail.com>
<[email protected]>
On Sun, May 3, 2026 at 11:45:53PM -0700, Christophe Pettus wrote:
>
>
> > On May 3, 2026, at 22:55, Ilya Kosmodemiansky <[email protected]>
> > 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.
--
Bruce Momjian <[email protected]> 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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: pgBackRest maintenance (was Re: Tablespace size in TB)
In-Reply-To: <[email protected]>
* 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