Horton

Re: Clear base backup progress reporting on error

Fujii Masao <masao.fujii@gmail.com>

View thread View on postgr.es
From: Fujii Masao <masao.fujii@gmail.com>
To: Chao Li <li.evan.chao@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2026-06-26T10:46:45Z
Lists: pgsql-hackers 
On Fri, Jun 26, 2026 at 5:59 PM Chao Li <li.evan.chao@gmail.com> wrote:
> This patch makes the following changes:

Thanks for the report and patch!

> I don’t think this is a serious bug, because with the usual pg_basebackup command path, the client normally disconnects after the error, so the stale progress entry is not observable. It is mainly visible when the same replication connection stays open after the failed BASE_BACKUP command. So I feel it might not be worth adding a TAP test.

+1

You may think this isn't worth backpatching to the stable branches
for the same reason?

Regards,

-- 
Fujii Masao

Commits

  1. Clear base backup progress on backup failure