On Fri, Jun 26, 2026 at 5:59 PM Chao Li <[email protected]> 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
