From 3c0cc47b6d435e3de95c0c8efd4f1ba5a0b84583 Mon Sep 17 00:00:00 2001
From: Elena Indrupskaya <e.indrupskaya@postgrespro.ru>
Date: Fri, 19 Feb 2021 16:30:07 +0300
Subject: [PATCH] [DOC] Recommendation on setting ptrack.map_size updated with
 ptrack documentation

---
 doc/pgprobackup.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/pgprobackup.xml b/doc/pgprobackup.xml
index 3ac4fdcd3..e0a733bde 100644
--- a/doc/pgprobackup.xml
+++ b/doc/pgprobackup.xml
@@ -1202,8 +1202,9 @@ CREATE EXTENSION ptrack;
        together, which leads to false-positive results when tracking changed
        blocks and increases the incremental backup size as unchanged blocks
        can also be copied into the incremental backup.
-       Setting <varname>ptrack.map_size</varname> to a higher value
-       does not affect PTRACK operation. The maximum allowed value is 1024.
+       Setting <varname>ptrack.map_size</varname> to a higher value does not
+       affect PTRACK operation, but it is not recommended to set this parameter
+       to a value higher than 1024.
       </para>
      </listitem>
     </orderedlist>