On Tue, Oct 13, 2026 at 5:50 AM surya poondla <[email protected]> wrote: > > Hi Daria, > > Thanks for v3.
Thanks for updating the patch! The documentation clarification below about the relationship between estimated backup size and compression addresses a separate issue from the incorrect progress reporting for incremental backups: + The approximate size of the archive that will be generated for the + tablespace, in kilobytes (1024 bytes), before any server-side + compression, if progress report has been requested; otherwise it's Rather than combining both fixes in one patch, how about splitting them into two patches? They address separate issues and have different backpatch ranges. The documentation clarification should be backpatched to v15, where server-side compression was introduced, while the incremental backup progress fix should be backpatched to v17. I've created both patches based on v3 patch and attached them. For the 0002 patch, I've also made some cosmetic changes and cleaned up the tests. Regards, -- Fujii Masao
v4-0001-doc-Clarify-that-base-backup-progress-counts-unco.patch
Description: Binary data
v4-0002-Report-correct-size-estimate-for-incremental-back.patch
Description: Binary data
