Re: Incremental backups report progress as if they were full backups

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Daria Lepikhova <daria(dot)n(dot)lepikhova(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Incremental backups report progress as if they were full backups
Date: 2026-10-06 20:55:50
Message-ID: CAN4CZFPAHAtcnrx92fEwegmQkWPjZRqhELKPDfMoL=6dkOq+xw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello!

- The approximate size of the tablespace, in kilobytes (1024 bytes),
- if progress report has been requested; otherwise it's null.
+ The approximate amount of data that will be sent for the
+ tablespace, in kilobytes (1024 bytes), if progress report has been
+ requested; otherwise it's null. For an incremental backup this can
+ be much smaller than the size of the tablespace, since files that
+ have changed only partially are sent as incremental files.

One nit to this: shouldn't it also mention unchanged files?

For example:

For an incremental backup this can be much smaller than the size of
the tablespace, since relation files that are unchanged or only partly
changed since the prior backup are sent as incremental files
containing just the modified blocks.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-10-06 21:15:29 Re: Session in aborted transaction misses effective_wal_level change
Previous Message Tristan Partin 2026-10-06 20:41:12 Re: Add counted_by attribute