|
35 | 35 | functions.
|
36 | 36 | </para>
|
37 | 37 | <para>
|
38 |
| - <filename>amcheck</> functions may be used only by superusers. |
| 38 | + <filename>amcheck</> functions may only be used by superusers. |
39 | 39 | </para>
|
40 | 40 |
|
41 | 41 | <sect2>
|
@@ -81,13 +81,12 @@ ORDER BY c.relpages DESC LIMIT 10;
|
81 | 81 | | pg_amop_fam_strat_index | 5
|
82 | 82 | (10 rows)
|
83 | 83 | </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. |
91 | 90 | </para>
|
92 | 91 | <para>
|
93 | 92 | <function>bt_index_check</function> acquires an <literal>AccessShareLock</>
|
@@ -230,8 +229,7 @@ ORDER BY c.relpages DESC LIMIT 10;
|
230 | 229 | </listitem>
|
231 | 230 | <listitem>
|
232 | 231 | <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. |
235 | 233 | </para>
|
236 | 234 | <para>
|
237 | 235 | <productname>PostgreSQL</> does not protect against correctable
|
|
0 commit comments