public inbox for pgsql-general@postgresql.org  

help / color / mirror / Atom feed

From: Christophe Pettus <xof@thebuild.com>
To: pgsql-general@lists.postgresql.org
Subject: pgBackRest maintenance (was Re: Tablespace size in TB)
Date: Sun, 3 May 2026 23:45:53 -0700
Message-ID: <DEBB18A6-E034-4222-B89A-99F3EB6EAF87@thebuild.com> (raw)
In-Reply-To: <CAG95seU1wFpHMLvLR+C1H9BDOK2jh_8RFxY3mmchtWUgMNu+ag@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>



> 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-suported fork will emerge if there were an existence proof of it happening in the PostgreSQL community.  I can't think of one.

We need to tell our customers something, and "the community will ride in and maintain pgBackRest, just you wait" isn't a satisfactory answer.  We can tell clients all we want that the current pgBackRest version works just fine, they don't have to change, a community standard version will emerge, and so forth, but that falls on deaf ears.  This is a backup tool; it's second only to PostgreSQL itself in the "must work all the time" camp.  All they hear is what it says on the repo, which is "pgBackRest is no longer being maintained."

I think it more likely that an entirely new backup tool will emerge, become the de facto community standards, and then we will move off pgBackRest (and its forks) onto that.

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: xof@thebuild.com, pgsql-general@lists.postgresql.org
  Subject: Re: pgBackRest maintenance (was Re: Tablespace size in TB)
  In-Reply-To: <DEBB18A6-E034-4222-B89A-99F3EB6EAF87@thebuild.com>

* 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