Date: Thu, 14 May 2026 13:26:45 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Christophe Pettus <xof@thebuild.com>
Cc: pgsql-general@lists.postgresql.org,
	Peter Eisentraut <peter@eisentraut.org>
Subject: Re: pgBackRest maintenance (was Re: Tablespace size in TB)
Message-ID: <agYF1Q6IVWwca0mH@momjian.us>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DEBB18A6-E034-4222-B89A-99F3EB6EAF87@thebuild.com>
Archived-At: 
 <https://www.postgresql.org/message-id/agYF1Q6IVWwca0mH%40momjian.us>
Precedence: bulk

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.

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