|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.94 2009/05/16 22:51:24 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.95 2009/06/17 13:59:28 petere Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="maintenance"> |
4 | 4 | <title>Routine Database Maintenance Tasks</title> |
@@ -603,7 +603,7 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb". |
603 | 603 |
|
604 | 604 | <para> |
605 | 605 | Tables whose <structfield>relfrozenxid</> value is more than |
606 | | - <varname>autovacuum_freeze_max_age</> transactions old are always |
| 606 | + <xref linkend="guc-autovacuum-freeze-max-age"> transactions old are always |
607 | 607 | vacuumed (this also applies to those tables whose freeze max age has |
608 | 608 | been modified via storage parameters; see below). Otherwise, if the |
609 | 609 | number of tuples obsoleted since the last |
|