aboutsummaryrefslogtreecommitdiff
path: root/src/backend/backup/basebackup_incremental.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2024-07-26 09:50:31 -0400
committerRobert Haas <rhaas@postgresql.org>2024-07-26 09:59:39 -0400
commitc7cfbc5157fec24704ea102f113d97193ffe5f7f (patch)
treef43edc01285c96d17f1b447bfd7c4c5f2487c17f /src/backend/backup/basebackup_incremental.c
parentc0c005070817352e217baa430b04161890d9af5a (diff)
downloadpostgresql-c7cfbc5157fec24704ea102f113d97193ffe5f7f.tar.gz
postgresql-c7cfbc5157fec24704ea102f113d97193ffe5f7f.zip
Allow WAL summarization to back up when timeline changes.
The old code believed that it was not possible to switch timelines without first replaying all of the WAL from the old timeline, but that turns out to be false, as demonstrated by an example from Fujii Masao. As a result, it assumed that summarization would always continue from the LSN where summarization previously ended. But in fact, when a timeline switch occurs without replaying all the WAL from the previous timeline, we can need to back up to an earlier LSN. Adjust accordingly. Discussion: https://postgr.es/m/CA+TgmoZGEsZodXC4f=XZNkAeyuDmWTSkpkjCEOcF19Am0mt_OA@mail.gmail.com
Diffstat (limited to 'src/backend/backup/basebackup_incremental.c')
0 files changed, 0 insertions, 0 deletions