Re: Clear base backup progress reporting on error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Clear base backup progress reporting on error
Date: 2026-07-05 23:40:50
Message-ID: 905434.1783294850@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> 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().

+1

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-07-06 00:33:35 Re: GIN amcheck leaks memory in gin_check_parent_keys_consistency
Previous Message Peter Smith 2026-07-05 23:39:45 Re: Proposal: Conflict log history table for Logical Replication