From d9b4da3e019662c269bb8d1497722c1d86a86197 Mon Sep 17 00:00:00 2001 From: Grigory Smolkin Date: Sat, 12 Oct 2019 15:08:49 +0300 Subject: [PATCH] Readme: update --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index b6675c87..8c20dafc 100644 --- a/README.md +++ b/README.md @@ -44,7 +44,6 @@ Regardless of the chosen backup type, all backups taken with `pg_probackup` supp `pg_probackup` currently has the following limitations: * 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. -* Remote mode is in beta stage. * Incremental chain can span only within one timeline. So if you have backup incremental chain taken from replica and it gets promoted, you would be forced to take another FULL backup. ## Current release