Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wNcAn-000wNY-1N for pgsql-general@arkaria.postgresql.org; Thu, 14 May 2026 19:56:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wNcAm-00Eoxa-0Q for pgsql-general@arkaria.postgresql.org; Thu, 14 May 2026 19:56:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wNcAl-00EoxR-2Z for pgsql-general@lists.postgresql.org; Thu, 14 May 2026 19:56:43 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wNcAj-00000000dLU-2Nfm for pgsql-general@lists.postgresql.org; Thu, 14 May 2026 19:56:43 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=69ktQwXTUet9Lx8Hh6es6VgslFra7xE4510IAgLL6Pk=; b=NBpIBYwXZEyWgicrh8YyvKsHwW 5bfLAiA9GbEGHH+kwcHmQu0P3rs/Sx9dE18pjkrj9e0ueo2X//fe1Vac/XYxiyenoah2NZGmP+PKU 0SBCsxgtF5UGBQoQsyuu1JqVTOC2XWCVvBuN/1K8I8KWzn0gbnCCOw1VJUja6wIrpXLBNJh3qOZ8D 5jFI9X0FXhRb4ztPHZye5SdRk6+iNuXz+cQZ4Lx8jJmZd3OAGqDeorYy9A21Y3XHDVX0CsOEvpeKx e51D6l81SeHs3s0J9JzfGthrwCBsJMaI6mDD1LB/KiPKzdSKkn6NmrpQmah6BC0Ex+EdfuPcIZzw7 XhxTNEAg==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wNcAg-0000000H618-3YGN; Thu, 14 May 2026 15:56:38 -0400 Date: Thu, 14 May 2026 15:56:38 -0400 From: Bruce Momjian To: Josef =?utf-8?B?xaBpbcOhbmVr?= Cc: Christophe Pettus , pgsql-general@lists.postgresql.org, Peter Eisentraut Subject: Re: pgBackRest maintenance (was Re: Tablespace size in TB) Message-ID: References: <81DB47B9-3244-41BA-980D-66AC371C8CA6@gmail.com> <3166829D-694D-4A44-B7F5-A7D454EB77DD@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, May 14, 2026 at 07:54:30PM +0200, Josef Šimánek wrote: > čt 14. 5. 2026 v 19:26 odesílatel Bruce Momjian napsal: > > > > On Sun, May 3, 2026 at 11:45:53PM -0700, Christophe Pettus wrote: > > > > > > > > > > On May 3, 2026, at 22:55, Ilya Kosmodemiansky > > > > 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. > > I think David is back and no fork is needed currently. > https://github.com/pgbackrest/pgbackrest/commit/b93a2b8807adabec02ef33cca838e30f109c3eba 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. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.