diff options
| author | Robert Haas <rhaas@postgresql.org> | 2024-07-25 15:45:06 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2024-07-25 16:09:24 -0400 |
| commit | de8b098ce567526e4da7d6e51cfe0fb132123ad7 (patch) | |
| tree | e9a0ed2827965514e7b6e3c46cae1ab3c75f9887 /src | |
| parent | 6622da8d3c7153fce58a35448f37a8869681625c (diff) | |
| download | postgresql-de8b098ce567526e4da7d6e51cfe0fb132123ad7.tar.gz postgresql-de8b098ce567526e4da7d6e51cfe0fb132123ad7.zip | |
Document restrictions regarding incremental backups and standbys.
If you try to take an incremental backup on a standby and there hasn't
been much system activity, it might fail. Document why this happens.
Also add a hint to the error message you get, to make it more likely
that users will understand what has gone wrong.
Laurenz Albe and Robert Haas
Discussion: https://postgr.es/m/5468641ad821dad7aa3b2d65bf843146443a1b68.camel@cybertec.at
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/backup/basebackup_incremental.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/backend/backup/basebackup_incremental.c b/src/backend/backup/basebackup_incremental.c index a8691b680df..cc2e168129a 100644 --- a/src/backend/backup/basebackup_incremental.c +++ b/src/backend/backup/basebackup_incremental.c @@ -441,7 +441,8 @@ PrepareForIncrementalBackup(IncrementalBackupInfo *ib, errmsg("manifest requires WAL from final timeline %u ending at %X/%X, but this backup starts at %X/%X", range->tli, LSN_FORMAT_ARGS(range->end_lsn), - LSN_FORMAT_ARGS(backup_state->startpoint)))); + LSN_FORMAT_ARGS(backup_state->startpoint)), + errhint("This can happen for incremental backups on a standby if there was little activity since the previous backup."))); } else { |