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
Performs logical verification of indexes for the specified
4193
4194
<productname>PostgreSQL</productname> instance if no corruption was found while checking
4194
-
data files. You must have the <application>amcheck</application>
4195
+
data files. You must have the <ulinkurl="https://postgrespro.com/docs/enterprise/current/amcheck.html"><application>amcheck</application></ulink>
4195
4196
extension or the <application>amcheck_next</application> extension
4196
4197
installed in the database to check its indexes. For databases
4197
4198
without <application>amcheck</application>, index verification will be skipped.
@@ -4211,8 +4212,10 @@ pg_probackup checkdb
4211
4212
installed in the database.
4212
4213
</para>
4213
4214
<para>
4214
-
This verification is only possible if it is supported by the version of the
4215
-
<application>amcheck</application> extension you are using.
4215
+
The verification of unique constraints is only possible if in the version of the
4216
+
<application>amcheck</application> extension you are using, the
4217
+
<function>bt_index_check</function> function takes the
4218
+
<parameter>checkunique</parameter> parameter.
4216
4219
</para>
4217
4220
</listitem>
4218
4221
</varlistentry>
@@ -4226,9 +4229,10 @@ pg_probackup checkdb
4226
4229
<option>--amcheck</option> flag.
4227
4230
</para>
4228
4231
<para>
4229
-
This check is only possible if it is supported by the version of the
4230
-
<application>amcheck</application> extension you are using or
4231
-
if the <application>amcheck_next</application> extension is used instead.
4232
+
This check is only possible if in the version of the
0 commit comments