<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.37 2005/07/30 15:45:49 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.38 2005/07/30 17:03:56 momjian Exp $
PostgreSQL documentation
-->
increase in I/O traffic, which cause poor performance for other active
sessions. Therefore, it is sometimes advisable to use
the cost-based vacuum delay feature. See <xref
- linkend="runtime" endterm="runtime-config-resource-vacuum-cost"> for more
+ linkend="runtime-config-resource-vacuum-cost"> for more
details.
</para>
</refsect1>
<simplelist type="inline">
<member><xref linkend="app-vacuumdb" endterm="app-vacuumdb-title"></member>
- <member><xref linkend="runtime" endterm="runtime-config-resource-vacuum-cost"></member>
+ <member><xref linkend="runtime-config-resource-vacuum-cost"></member>
</simplelist>
</refsect1>
</refentry>