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

Commit0ad017f

Browse files
committed
Update various obsolete remarks about VACUUM.
1 parentea6f2e6 commit0ad017f

File tree

4 files changed

+25
-27
lines changed

4 files changed

+25
-27
lines changed

‎doc/src/sgml/backup.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.18 2001/11/12 19:19:39 petere Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.19 2001/11/18 22:17:30 tgl Exp $ -->
22
<chapter id="backup">
33
<title>Backup and Restore</title>
44

@@ -76,7 +76,7 @@ pg_dump <replaceable class="parameter">dbname</replaceable> &gt; <replaceable cl
7676
running will not be in the dump. <application>pg_dump</> does not
7777
block other operations on the database while it is working.
7878
(Exceptions are those operations that need to operate with an
79-
exclusive lock, such as <command>VACUUM</command>.)
79+
exclusive lock, such as <command>VACUUM FULL</command>.)
8080
</para>
8181

8282
<important>

‎doc/src/sgml/maintenance.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.6 2001/11/12 19:19:39 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.7 2001/11/18 22:17:30 tgl Exp $
33
-->
44

55
<chapter id="maintenance">
@@ -105,8 +105,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.6 2001/11/12 19:19:39
105105
In normal <productname>PostgreSQL</productname> operation, an UPDATE or
106106
DELETE of a row does not immediately remove the old <firstterm>tuple</>
107107
(version of the row). This approach is necessary to gain the benefits
108-
of multiversion concurrency control (see the User's Guide): the tuple
109-
must not be deleted while
108+
of multiversion concurrency control (see the<citetitle>User's Guide</>):
109+
the tuplemust not be deleted while
110110
it is still potentially visible to other transactions. But eventually,
111111
an outdated or deleted tuple is no longer of interest to any transaction.
112112
The space it occupies must be reclaimed for reuse by new tuples, to avoid

‎doc/src/sgml/ref/analyze.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.3 2001/10/16 01:13:44 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.4 2001/11/18 22:17:30 tgl Exp $
33
Postgres documentation
44
-->
55

@@ -125,12 +125,12 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ (<rep
125125
just after making major changes in the contents of a table. Accurate
126126
statistics will help the planner to choose the most appropriate query
127127
plan, and thereby improve the speed of query processing. A common
128-
strategy is to run <command>VACUUM</command> and <command>ANALYZE</command>
129-
once a day during a low-usage time of day.
128+
strategy is to run <xref linkend="sql-vacuum" endterm="sql-vacuum-title">
129+
and <command>ANALYZE</command>once a day during a low-usage time of day.
130130
</para>
131131

132132
<para>
133-
Unlike <xref linkend="sql-vacuum" endterm="sql-vacuum-title">,
133+
Unlike <command>VACUUM FULL</command>,
134134
<command>ANALYZE</command> requires
135135
only a read lock on the target table, so it can run in parallel with
136136
other activity on the table.

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

Lines changed: 16 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.20 2001/10/12 23:34:30momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.21 2001/11/18 22:17:30tgl Exp $
33
Postgres documentation
44
-->
55

@@ -207,8 +207,7 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
207207
intended usage is in connection with preparation of user-defined template
208208
databases, or other databases that are completely read-only and will not
209209
receive routine maintenance <command>VACUUM</> operations.
210-
See <xref linkend="sql-createdatabase" endterm="sql-createdatabase-title">
211-
for details.
210+
See the <citetitle>Administrator's Guide</> for details.
212211
</para>
213212

214213
<refsect2 id="R2-SQL-VACUUM-3">
@@ -222,8 +221,7 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
222221
<para>
223222
We recommend that active production databases be
224223
<command>VACUUM</command>-ed frequently (at least nightly), in order to
225-
remove expired rows. After copying a large table into
226-
<productname>Postgres</productname> or after deleting a large number
224+
remove expired rows. After adding or deleting a large number
227225
of records, it may be a good idea to issue a <command>VACUUM
228226
ANALYZE</command> command for the affected table. This will update the
229227
system catalogs with
@@ -254,19 +252,19 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
254252
<programlisting>
255253
regression=> VACUUM VERBOSE ANALYZE onek;
256254
NOTICE: --Relation onek--
257-
NOTICE:Pages 98: Changed 25, Reapped 74, Empty 0, New 0;
258-
Tup 1000: Vac 3000, Crash 0, UnUsed 0, MinLen 188, MaxLen 188;
259-
Re-using: Free/Avail. Space 586952/586952; EndEmpty/Avail. Pages 0/74.
260-
Elapsed 0/0 sec.
261-
NOTICE: Indexonek_stringu1: Pages28; Tuples 1000: Deleted 3000. Elapsed 0/0 sec.
262-
NOTICE: Index onek_hundred: Pages 12; Tuples 1000: Deleted 3000. Elapsed 0/0 sec.
263-
NOTICE: Indexonek_unique2: Pages19; Tuples 1000: Deleted 3000. Elapsed 0/0 sec.
264-
NOTICE: Index onek_unique1: Pages 17; Tuples 1000: Deleted 3000. Elapsed 0/0 sec.
265-
NOTICE:Rel onek: Pages: 98 --> 25; Tuple(s) moved: 1000. Elapsed 0/1 sec.
266-
NOTICE: Index onek_stringu1: Pages 28; Tuples 1000: Deleted 1000. Elapsed 0/0 sec.
267-
NOTICE:Index onek_hundred: Pages 12; Tuples 1000:Deleted 1000. Elapsed 0/0 sec.
268-
NOTICE: Index onek_unique2: Pages 19; Tuples 1000: Deleted 1000. Elapsed 0/0 sec.
269-
NOTICE:Index onek_unique1: Pages 17; Tuples 1000: Deleted 1000. Elapsed 0/0 sec.
255+
NOTICE:Index onek_unique1: Pages 14; Tuples 1000: Deleted 3000.
256+
CPU 0.00s/0.11u sec elapsed 0.12 sec.
257+
NOTICE: Index onek_unique2: Pages 16; Tuples 1000: Deleted 3000.
258+
CPU 0.00s/0.10u sec elapsed 0.10 sec.
259+
NOTICE: Indexonek_hundred: Pages13; Tuples 1000: Deleted 3000.
260+
CPU 0.00s/0.10u sec elapsed 0.10 sec.
261+
NOTICE: Indexonek_stringu1: Pages31; Tuples 1000: Deleted 3000.
262+
CPU 0.01s/0.09u sec elapsed 0.10 sec.
263+
NOTICE:Removed 3000 tuples in 70 pages.
264+
CPU 0.02s/0.04u sec elapsed 0.07 sec.
265+
NOTICE:Pages 94: Changed 0, Empty 0; Tup 1000:Vac 3000, Keep 0, UnUsed 0.
266+
Total CPU 0.05s/0.45u sec elapsed 0.59 sec.
267+
NOTICE:Analyzing onek
270268
VACUUM
271269
</programlisting>
272270
</para>

0 commit comments

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