Request a Demo
Home   >   mailing lists

Re: Clear base backup progress reporting on error - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Clear base backup progress reporting on error
Date
Msg-id CAHGQGwEwt8wTWMPr7Xt5wBAn-FnVEHRwVbxc2AxiVZDEAbezWg@mail.gmail.com
Whole thread
In response to Re: Clear base backup progress reporting on error  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Tree view 
On Sat, Jul 4, 2026 at 11:17 PM Andrew Dunstan <andrew@dunslane.net> wrote:
> This has upset the ABI compliance checker (see
<https://buildfarm.postgresql.org/cgi-bin/show_failures.pl?max_days=3&stage=abi-compliance-check&filter=Submit>. Looks
likeyou need to update the  .abi-compliance-history file on the affected back branches. 

Thanks for pointing out this! That's my mistake...

The ABI break was caused by removing the external function
basebackup_progress_done(). I think the better fix for the stable branches
is to restore that function, even though PostgreSQL core itself no longer
uses it, rather than updating the .abi-compliance-history file. Because
some external backup tools may still be calling basebackup_progress_done().
Thoughts?

Regards,

--
Fujii Masao

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: pg_dump: use threads for parallel workers on all platforms
Next
From: Fujii Masao
Date:
Subject: Re: Clear base backup progress reporting on error