@@ -1161,14 +1161,22 @@ GRANT SELECT ON TABLE pg_catalog.pg_database TO backup;
11611161 PostgreSQL. Links to PTRACK patches can be found
11621162 <ulink url =" https://github.com/postgrespro/pg_probackup#ptrack-support" >here</ulink >.
11631163 </para >
1164+ <note >
1165+ <para >
1166+ PTRACK versions lower than 2.0 are deprecated. Postgres Pro Standard and Postgres Pro Enterprise
1167+ versions starting with 11.9.1 contain PTRACK 2.0. Upgrade your server to avoid issues in backups
1168+ that you will take in future and be sure to take fresh backups of your clusters with the upgraded
1169+ PTRACK since the backups taken with PTRACK 1.x might be corrupt.
1170+ </para >
1171+ </note >
11641172 <para >
11651173 If you are going to use PTRACK backups, complete the following
11661174 additional steps. The role that will perform PTRACK backups
11671175 (the <literal >backup</literal > role in the examples below) must have
11681176 access to all the databases of the cluster.
11691177 </para >
11701178 <para >
1171- For <productname >PostgreSQL</productname >12 or higher:
1179+ For <productname >PostgreSQL</productname >11 or higher:
11721180 </para >
11731181 <orderedlist >
11741182 <listitem >
@@ -1226,7 +1234,7 @@ GRANT EXECUTE ON FUNCTION pg_ptrack_get_block(oid, oid, oid, bigint) TO backup;
12261234 For older <productname >PostgreSQL</productname > versions,
12271235 PTRACK required taking backups in the exclusive mode
12281236 to provide exclusive access to bitmaps with changed blocks.
1229- To set up PTRACK backups for <productname >PostgreSQL</productname >11
1237+ To set up PTRACK backups for <productname >PostgreSQL</productname >10
12301238 or lower, do the following:
12311239 </para >
12321240 <orderedlist >