Update documents on incremenal backup

Author: Jubilee101

README.md

@@ -7,6 +7,7 @@
 ## Features
 
 * Full backup
+* Incremental backup (PostgreSQL 17+)
 * Restore
 * Compression (gzip, zstd, lz4, bzip2)
 * AES encryption support

doc/manual/advanced/06-retention.md

@@ -31,9 +31,7 @@ This is a very hard property to configure since it depends on the size of the da
 
 If you want to restore from the latest backup plus the Write-Ahead Log (WAL) then the default [**pgmoneta**](pgmoneta) policy maybe is enough.
 
-Note that currently if a backup has an incremental backup child that depends on it, it will be kept even if it doesn't
-
-fall under retention policy. We will support incremental backup deletion in later releases.
+Note that if a backup has an incremental backup child that depends on it, its data will be rolled up to its child before getting deleted.
 
 ## Retention check
 

doc/manual/advanced/07-keep.md

@@ -81,9 +81,6 @@ Response:
 
 and you can see that the backup has a `Keep` flag of `true`.
 
-Note that `Keep` currently only works on full backups, we will
-support keeping incremental backups in later releases.
-
 ## Describe a backup
 
 Now, you may want to add a description to your backup, and as you can see

doc/tutorial/07_delete.md

@@ -17,7 +17,7 @@ pgmoneta-cli -c pgmoneta.conf delete primary oldest
 
 will delete the oldest backup on `[primary]`.
 
-Note that currently delete will fail if the backup has an incremental backup child that depends on it.
-We will support incremental backup deletion in later releases.
+Note that if the backup has an incremental backup child that depends on it,
+its data will be rolled up to its child before getting deleted.
 
 (`pgmoneta` user)

doc/tutorial/09_retention.md

@@ -17,8 +17,7 @@ all the backups within the nearest 7 days, the latest backup on each Monday with
 the latest backup on the first day of each month in the last 12 months and the latest backup on the first
 day of each year in the last 5 years. If you input more than 4 values, [**pgmoneta**](https://github.com/pgmoneta/pgmoneta) will only read the first 4.
 
-Note that currently if a backup has an incremental backup child that depends on it, it will be kept even if it doesn't
-fall under retention policy. We will support incremental backup deletion in later releases.
+Note that if a backup has an incremental backup child that depends on it, its data will be rolled up to its child before getting deleted.
 
 There are a lot of ways to leave a parameter unspecified. For trailing parameters, you can simply omit them.
 And for parameters in between, you can use placeholders. Currently, placeholders we allow are: `-`, `X`, `x`, `0`

doc/tutorial/13_hot_standby.md

@@ -27,8 +27,6 @@ hot_standby_overrides = /your/local/hot/standby/overrides/
 
 to override files in the `hot_standby` directory.
 
-Note that currently hot standby doesn't work with incremental backups, this will be supported in later releases.
-
 ### Tablespaces
 
 By default tablespaces will be mapped to a similar path than the original one, for example `/tmp/mytblspc` becomes `/tmp/mytblspchs`.