database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-12-19 17:02:53 +03:00
Code Activity

Use "dead" rather than "expired" for vacuumable rows.

Browse Source
This commit is contained in:
Bruce Momjian
2006-12-27 14:55:17 +00:00
parent 0cbc5b1ed4
commit 4f1e49119e
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/ref/vacuum.sgml
View File

@@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.44 2006/12/23 01:58:40 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.45 2006/12/27 14:55:17 momjian Exp $
PostgreSQL documentation
-->
@@ -29,7 +29,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
<title>Description</title>
<para>
<command>VACUUM</command> reclaims storage occupied by expired tuples.
<command>VACUUM</command> reclaims storage occupied by dead tuples.
In normal <productname>PostgreSQL</productname> operation, tuples that
are deleted or obsoleted by an update are not physically removed from
their table; they remain present until a <command>VACUUM</command> is
@@ -152,7 +152,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
<para>
We recommend that active production databases be
vacuumed frequently (at least nightly), in order to
remove expired rows. After adding or deleting a large number
remove dead rows. After adding or deleting a large number
of rows, it may be a good idea to issue a <command>VACUUM
ANALYZE</command> command for the affected table. This will update the
system catalogs with