From 5724c0bbd3af7183cbb02a8327e968fe0c4a9244 Mon Sep 17 00:00:00 2001 From: Mireia Perez Date: Thu, 13 Aug 2026 15:01:43 +0100 Subject: [PATCH] Add COPY.. FROM to the list that triggers incremental backup --- docs/whpg-backup/incremental.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/whpg-backup/incremental.md b/docs/whpg-backup/incremental.md index 242a20a..7ab4e45 100644 --- a/docs/whpg-backup/incremental.md +++ b/docs/whpg-backup/incremental.md @@ -15,6 +15,7 @@ Use `gpbackup` and `gprestore` to create and restore incremental backups of appe - `TRUNCATE` - `UPDATE` - `DROP` and then re-create the table +- `COPY .. FROM` An incremental backup always includes every specified heap table, and backs up an append-optimized table, including a column-oriented table, only if it's changed. An incremental backup set consists of a full backup, plus the incremental backups that capture changes to the database since that full backup. For example, a full backup on Sunday plus three daily incremental backups on Monday, Wednesday, and Friday together form one backup set. Restoring from an incremental backup requires the complete backup set, and every backup in a set must use consistent command-line options so that `gpbackup` can build on it and `gprestore` can restore from it.