You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,11 +48,11 @@ Regardless of the chosen backup type, all backups taken with `pg_probackup` supp
48
48
49
49
`pg_probackup` currently has the following limitations:
50
50
* The server from which the backup was taken and the restored server must be compatible by the[block_size](https://postgrespro.com/docs/postgresql/current/runtime-config-preset#GUC-BLOCK-SIZE) and[wal_block_size](https://postgrespro.com/docs/postgresql/current/runtime-config-preset#GUC-WAL-BLOCK-SIZE) parameters and have the same major release number.
51
-
*Incremental chain can span only within one timeline. So if you havebackupincremental chain taken from replica and it gets promoted, you would be forced to take another FULL backup.
51
+
*Remotebackupvia ssh on Windows currently is not supported.