Skip to content

Commit f85537a

Browse files
Doc: Correct description of amcheck example query.
The amcheck documentation incorrectly claimed that its example query verifies every catalog index in the database. In fact, the query only verifies the 10 largest indexes (as determined by pg_class.relpages). Adjust the description accordingly. Backpatch: 10-, where contrib/amcheck was introduced.
1 parent 2332020 commit f85537a

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

doc/src/sgml/amcheck.sgml

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@
3535
functions.
3636
</para>
3737
<para>
38-
<filename>amcheck</> functions may be used only by superusers.
38+
<filename>amcheck</> functions may only be used by superusers.
3939
</para>
4040

4141
<sect2>
@@ -81,13 +81,12 @@ ORDER BY c.relpages DESC LIMIT 10;
8181
| pg_amop_fam_strat_index | 5
8282
(10 rows)
8383
</screen>
84-
This example shows a session that performs verification of every
85-
catalog index in the database <quote>test</>. Details of just
86-
the 10 largest indexes verified are displayed. Since no error
87-
is raised, all indexes tested appear to be logically consistent.
88-
Naturally, this query could easily be changed to call
89-
<function>bt_index_check</function> for every index in the
90-
database where verification is supported.
84+
This example shows a session that performs verification of the
85+
10 largest catalog indexes in the database <quote>test</>.
86+
Since no error is raised, all indexes tested appear to be
87+
logically consistent. Naturally, this query could easily be
88+
changed to call <function>bt_index_check</function> for every
89+
index in the database where verification is supported.
9190
</para>
9291
<para>
9392
<function>bt_index_check</function> acquires an <literal>AccessShareLock</>
@@ -230,8 +229,7 @@ ORDER BY c.relpages DESC LIMIT 10;
230229
</listitem>
231230
<listitem>
232231
<para>
233-
Corruption caused by faulty RAM, and the broader memory subsystem
234-
and operating system.
232+
Corruption caused by faulty RAM, or the broader memory subsystem.
235233
</para>
236234
<para>
237235
<productname>PostgreSQL</> does not protect against correctable

0 commit comments

Comments
 (0)