| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: pgBackRest maintenance (was Re: Tablespace size in TB) |
| Date: | 2026-05-14 17:26:45 |
| Message-ID: | agYF1Q6IVWwca0mH@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, May 3, 2026 at 11:45:53PM -0700, Christophe Pettus wrote:
>
>
> > On May 3, 2026, at 22:55, Ilya Kosmodemiansky <ik(at)dataegret(dot)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(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josef Šimánek | 2026-05-14 17:54:30 | Re: pgBackRest maintenance (was Re: Tablespace size in TB) |
| Previous Message | Ron Johnson | 2026-05-14 17:20:12 | Re: Alter the datatype on all tables present in the database (bigint to varchar) |