diff options
| author | Andrew Dunstan <andrew@dunslane.net> | 2024-04-09 15:30:48 -0400 |
|---|---|---|
| committer | Andrew Dunstan <andrew@dunslane.net> | 2024-04-12 10:32:30 -0400 |
| commit | 42fa4b660143b66bea1fb90793ec90054e170c93 (patch) | |
| tree | 058096389cf8c17ab2dceb0b8b9fb7bf55ad522c /src/backend/backup/basebackup_incremental.c | |
| parent | b8a7bfa33324bc40c7180cb946a39378fb48309c (diff) | |
| download | postgresql-42fa4b660143b66bea1fb90793ec90054e170c93.tar.gz postgresql-42fa4b660143b66bea1fb90793ec90054e170c93.zip | |
Assorted minor cleanups in the test_json_parser module
Per gripes from Michael Paquier
Discussion: https://postgr.es/m/ZhTQ6_w1vwOhqTQI@paquier.xyz
Along the way, also clean up a handful of typos in 3311ea86ed and
ea7b4e9a2a, found by Alexander Lakhin, and a couple of stylistic
snafus noted by Daniel Westermann and Daniel Gustafsson.
Diffstat (limited to 'src/backend/backup/basebackup_incremental.c')
| -rw-r--r-- | src/backend/backup/basebackup_incremental.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/backup/basebackup_incremental.c b/src/backend/backup/basebackup_incremental.c index 330a2294011..4ad9d7cad00 100644 --- a/src/backend/backup/basebackup_incremental.c +++ b/src/backend/backup/basebackup_incremental.c @@ -34,7 +34,7 @@ #define BLOCKS_PER_READ 512 /* - * we expect the find the last lines of the manifest, including the checksum, + * We expect to find the last lines of the manifest, including the checksum, * in the last MIN_CHUNK bytes of the manifest. We trigger an incremental * parse step if we are about to overflow MAX_CHUNK bytes. */ @@ -88,8 +88,8 @@ struct IncrementalBackupInfo * Files extracted from the backup manifest. * * We don't really need this information, because we use WAL summaries to - * figure what's changed. It would be unsafe to just rely on the list of - * files that existed before, because it's possible for a file to be + * figure out what's changed. It would be unsafe to just rely on the list + * of files that existed before, because it's possible for a file to be * removed and a new one created with the same name and different * contents. In such cases, the whole file must still be sent. We can tell * from the WAL summaries whether that happened, but not from the file |