MIME-Version: 1.0
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>
 <agYo9iveYcCHeKGt@momjian.us>
 <CAFp7QwoRSy2dwF1j=yqX_AdQc05r2gpD89_L-EGVM=vN+aOE4A@mail.gmail.com>
In-Reply-To: 
 <CAFp7QwoRSy2dwF1j=yqX_AdQc05r2gpD89_L-EGVM=vN+aOE4A@mail.gmail.com>
From: =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= <josef.simanek@gmail.com>
Date: Fri, 15 May 2026 03:09:08 +0200
Message-ID: 
 <CAFp7QwpErUZLWsYyKZG5t7j7X=5NkebOpaQLyCvrThr_p0yvcg@mail.gmail.com>
Subject: Re: pgBackRest maintenance (was Re: Tablespace size in TB)
To: Bruce Momjian <bruce@momjian.us>
Cc: Christophe Pettus <xof@thebuild.com>, pgsql-general@lists.postgresql.org,
	Peter Eisentraut <peter@eisentraut.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAFp7QwpErUZLWsYyKZG5t7j7X%3D5NkebOpaQLyCvrThr_p0yvcg%40mail.gmail.com>
Precedence: bulk

=C4=8Dt 14. 5. 2026 v 22:10 odes=C3=ADlatel Josef =C5=A0im=C3=A1nek
<josef.simanek@gmail.com> napsal:
>
> =C4=8Dt 14. 5. 2026 v 21:56 odes=C3=ADlatel Bruce Momjian <bruce@momjian.=
us> napsal:
> >
> > On Thu, May 14, 2026 at 07:54:30PM +0200, Josef =C5=A0im=C3=A1nek wrote=
:
> > > =C4=8Dt 14. 5. 2026 v 19:26 odes=C3=ADlatel Bruce Momjian <bruce@momj=
ian.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 patien=
ce.
> > > > >
> > > > > Dave was quite clear that someone "picking up the pgBackRest proj=
ect"
> > > > > 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 pro=
of
> > > > > of it happening in the PostgreSQL community.  I can't think of on=
e.
> > > >
> > > > That happened with pgbouncer where development stopped and a new te=
am
> > > > picked it up.  I think Peter Eisentraut was involved.  With pgbackr=
est,
> > > > 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/b93a2b8807adabec02ef3=
3cca838e30f109c3eba
> >
> > 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.
>
> Website was also updated, but seems not deployed.
> https://github.com/pgbackrest/website/commit/5516003b0f19900fe702b8afd1bc=
70bc16fede43
> I have reported.

site is updated now https://pgbackrest.org/

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