| From: | David Steele <david(at)pgbackrest(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Subject: | Re: Return pg_control from pg_backup_stop(). |
| Date: | 2026-06-30 05:15:19 |
| Message-ID: | 86436ff9-eb98-4c8a-825e-3bcae022107b@pgbackrest.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/13/26 21:55, David Steele wrote:
>
> I have withdrawn this patch. If anybody wants to pick it up in the
> future I'll be happy to rebase it but I think two years is long enough
> to maintain a patch that is not getting traction.
I would like to revive this but focus on the first patch for now and
drop the second patch from consideration.
The patch now implements only the new flag for pgcontrol and wires this
logic into basebackup. It has the additional benefit of guaranteeing
that the base backup contains a non-torn version of pgcontrol.
I know everyone was really busy in March but now that things are a bit
calmer I'd like to revisit.
Heikki, Robert, Andres, Fujii -- any objections or comments? I believe
Michael is on board with the feature (this part, at least) but he very
sensibly would like to have some consensus.
Thanks,
-David
| Attachment | Content-Type | Size |
|---|---|---|
| pgcontrol-basebackup-flag-v11.patch | text/plain | 12.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2026-06-30 05:22:14 | Re: Add per-backend lock statistics |
| Previous Message | Michael Paquier | 2026-06-30 04:47:41 | Re: Handle concurrent drop when doing whole database vacuum |