|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.66 2007/01/16 18:26:02 alvherre Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.67 2007/01/31 04:13:22 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="maintenance">
|
4 | 4 | <title>Routine Database Maintenance Tasks</title>
|
@@ -615,9 +615,7 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu
|
615 | 615 | for inefficient use of space: if all but a few index keys on a page have
|
616 | 616 | been deleted, the page remains allocated. So a usage pattern in which all
|
617 | 617 | but a few keys in each range are eventually deleted will see poor use of
|
618 |
| - space. The potential for bloat is not indefinite — at worst there |
619 |
| - will be one key per page — but it may still be worthwhile to schedule |
620 |
| - periodic reindexing for indexes that have such usage patterns. |
| 618 | + space. For such usage patterns, periodic reindexing is recommended. |
621 | 619 | </para>
|
622 | 620 |
|
623 | 621 | <para>
|
|