aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-02-06 14:40:31 +0900
committerMichael Paquier <michael@paquier.xyz>2023-02-06 14:40:31 +0900
commitd07c2948bfe577cfeaa4eb564c5e62bcb6cb1955 (patch)
tree4771a0cd44cff7fc894dcbfa6e113eba25595cf9 /src/backend/access/gist/gistbuild.c
parent71c37797d7bd78266146a5829ab62b3687c47295 (diff)
downloadpostgresql-d07c2948bfe577cfeaa4eb564c5e62bcb6cb1955.tar.gz
postgresql-d07c2948bfe577cfeaa4eb564c5e62bcb6cb1955.zip
Add support for progress reporting to pg_verifybackup
This adds a new option to pg_verifybackup called -P/--progress, showing every second some information about the progress of the checksum verification based on the data of a backup manifest. Similarly to what is done for pg_rewind and pg_basebackup, the information printed in the progress report consists of the current amount of data computed and the total amount of data that will be computed. Note that files found with an incorrect size do not have their checksum verified, hence their size is not appended to the total amount of data estimated during the first scan of the manifest data (such incorrect sizes could be overly high, for one, falsifying the progress report). Author: Masahiko Sawada Discussion: https://postgr.es/m/CAD21AoC5+JOgMd4o3z_oxw0f8JDSsCYY7zSbhe-O9x7f33rw_A@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions