Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit4f1e491

Browse files
committed
Use "dead" rather than "expired" for vacuumable rows.
1 parent0cbc5b1 commit4f1e491

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

‎doc/src/sgml/maintenance.sgml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.64 2006/11/05 22:42:07 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.65 2006/12/27 14:55:17 momjian Exp $ -->
22

33
<chapter id="maintenance">
44
<title>Routine Database Maintenance Tasks</title>
@@ -142,9 +142,9 @@
142142
<para>
143143
There are two variants of the <command>VACUUM</command>
144144
command. The first form, known as <quote>lazy vacuum</quote> or
145-
just <command>VACUUM</command>, marksexpired data in tables and
145+
just <command>VACUUM</command>, marksdead data in tables and
146146
indexes for future reuse; it does <emphasis>not</emphasis> attempt
147-
to reclaim the space used by thisexpired data unless the space is
147+
to reclaim the space used by thisdead data unless the space is
148148
at the end of the table and an exclusive table lock can be easily
149149
obtained. Unused space at the start or middle of the file does
150150
not result in the file being shortened and space returned to the
@@ -155,7 +155,7 @@
155155
<para>
156156
The second form is the <command>VACUUM FULL</command>
157157
command. This uses a more aggressive algorithm for reclaiming the
158-
space consumed byexpired row versions. Any space that is freed by
158+
space consumed bydead row versions. Any space that is freed by
159159
<command>VACUUM FULL</command> is immediately returned to the
160160
operating system. Unfortunately, this variant of the
161161
<command>VACUUM</command> command acquires an exclusive lock on

‎doc/src/sgml/ref/vacuum.sgml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.44 2006/12/23 01:58:40 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.45 2006/12/27 14:55:17 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -29,7 +29,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
2929
<title>Description</title>
3030

3131
<para>
32-
<command>VACUUM</command> reclaims storage occupied byexpired tuples.
32+
<command>VACUUM</command> reclaims storage occupied bydead tuples.
3333
In normal <productname>PostgreSQL</productname> operation, tuples that
3434
are deleted or obsoleted by an update are not physically removed from
3535
their table; they remain present until a <command>VACUUM</command> is
@@ -152,7 +152,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
152152
<para>
153153
We recommend that active production databases be
154154
vacuumed frequently (at least nightly), in order to
155-
removeexpired rows. After adding or deleting a large number
155+
removedead rows. After adding or deleting a large number
156156
of rows, it may be a good idea to issue a <command>VACUUM
157157
ANALYZE</command> command for the affected table. This will update the
158158
system catalogs with

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp