Re: Return pg_control from pg_backup_stop().

From: Shaun Thomas <shaun(dot)thomas(at)pgedge(dot)com>
To: Andy Pogrebnoi <andrew(dot)pogrebnoi(at)percona(dot)com>
Cc: David Steele <david(at)pgbackrest(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Haibo Yan <tristan(dot)yim(at)gmail(dot)com>, 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-07-30 22:02:45
Message-ID: CAPEjYe=QxL7Hn5CCcMpOm9use+s-ZhB2=NAOJPvDvy6DJaum=A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> It'd be great to have 01 committed. It seems to me like a solid and low cost
> solution for the torn pg_control (and missed backup lables). These are good
> improvements for base backups.

I'd like to second this, if possible. It's not exactly a "glamorous" or
critical issue, but this _does_ address a known issue re: torn pg_control if
nothing else. Based on the conversation I saw here, it seems like there's no
impetus so the patch is merely languishing, sans any lingering unaddressed
criticism.

Does it just need a committer to take ownership?

--
Shaun Thomas
Principal Software Engineer
shaun(dot)thomas(at)pgEdge(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Wong 2026-07-30 22:54:10 Re: real/float example for testlibpq3
Previous Message Zsolt Parragi 2026-07-30 22:02:31 Re: datachecksums: handle invalid and dropped databases during enable