|
35 | 35 | functions. |
36 | 36 | </para> |
37 | 37 | <para> |
38 | | - <filename>amcheck</filename> functions may be used only by superusers. |
| 38 | + <filename>amcheck</filename> functions mayonlybe used by superusers. |
39 | 39 | </para> |
40 | 40 |
|
41 | 41 | <sect2> |
@@ -83,14 +83,13 @@ ORDER BY c.relpages DESC LIMIT 10; |
83 | 83 | | pg_amop_fam_strat_index | 5 |
84 | 84 | (10 rows) |
85 | 85 | </screen> |
86 | | - This example shows a session that performs verification of every |
87 | | - catalog index in the database <quote>test</quote>. Details of just |
88 | | - the 10 largest indexes verified are displayed. Verification of |
89 | | - the presence of heap tuples as index tuples is requested for |
90 | | - unique indexes only. Since no error is raised, all indexes |
91 | | - tested appear to be logically consistent. Naturally, this query |
92 | | - could easily be changed to call |
93 | | - <function>bt_index_check</function> for every index in the |
| 86 | + This example shows a session that performs verification of the |
| 87 | + 10 largest catalog indexes in the database <quote>test</quote>. |
| 88 | + Verification of the presence of heap tuples as index tuples is |
| 89 | + requested for the subset that are unique indexes. Since no |
| 90 | + error is raised, all indexes tested appear to be logically |
| 91 | + consistent. Naturally, this query could easily be changed to |
| 92 | + call <function>bt_index_check</function> for every index in the |
94 | 93 | database where verification is supported. |
95 | 94 | </para> |
96 | 95 | <para> |
@@ -292,8 +291,7 @@ ORDER BY c.relpages DESC LIMIT 10; |
292 | 291 | </listitem> |
293 | 292 | <listitem> |
294 | 293 | <para> |
295 | | - Corruption caused by faulty RAM, and the broader memory subsystem |
296 | | - and operating system. |
| 294 | + Corruption caused by faulty RAM, or the broader memory subsystem. |
297 | 295 | </para> |
298 | 296 | <para> |
299 | 297 | <productname>PostgreSQL</productname> does not protect against correctable |
|