aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/matview.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2024-03-13 15:04:22 -0400
committerRobert Haas <rhaas@postgresql.org>2024-03-13 15:12:33 -0400
commit2041bc4276c95ac014510032e622a4baf70b29f1 (patch)
tree7fb89a55324b84f867d8cc1a1f83f3541c1ad484 /src/backend/commands/matview.c
parent1ee910ce437188eab40eddf32dc7d81952e99f82 (diff)
downloadpostgresql-2041bc4276c95ac014510032e622a4baf70b29f1.tar.gz
postgresql-2041bc4276c95ac014510032e622a4baf70b29f1.zip
Add the system identifier to backup manifests.
Before this patch, if you took a full backup on server A and then tried to use the backup manifest to take an incremental backup on server B, it wouldn't know that the manifest was from a different server and so the incremental backup operation could potentially complete without error. When you later tried to run pg_combinebackup, you'd find out that your incremental backup was and always had been invalid. That's poor timing, because nobody likes finding out about backup problems only at restore time. With this patch, you'll get an error when trying to take the (invalid) incremental backup, which seems a lot nicer. Amul Sul, revised by me. Review by Michael Paquier. Discussion: http://postgr.es/m/CA+TgmoYLZzbSAMM3cAjV4Y+iCRZn-bR9H2+Mdz7NdaJFU1Zb5w@mail.gmail.com
Diffstat (limited to 'src/backend/commands/matview.c')
0 files changed, 0 insertions, 0 deletions