1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>VACUUM</title>
<link rel="stylesheet" href="stylesheet.css" type="text/css">
<link rev="made" href="pgsql-docs@postgresql.org">
<meta name="generator" content="DocBook XSL Stylesheets V1.70.0">
<link rel="start" href="index.html" title="PostgreSQL 8.1.4 Documentation">
<link rel="up" href="sql-commands.html" title="SQL Commands">
<link rel="prev" href="sql-update.html" title="UPDATE">
<link rel="next" href="reference-client.html" title="PostgreSQL Client Applications">
<link rel="copyright" href="ln-legalnotice.html" title="Legal Notice">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en">
<a name="sql-vacuum"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2>Name</h2>
<p>VACUUM — garbage-collect and optionally analyze a database</p>
</div>
<a name="id790721"></a><div class="refsynopsisdiv">
<h2>Synopsis</h2>
<pre class="synopsis">VACUUM [ FULL | FREEZE ] [ VERBOSE ] [ <em class="replaceable"><code>table</code></em> ]
VACUUM [ FULL | FREEZE ] [ VERBOSE ] ANALYZE [ <em class="replaceable"><code>table</code></em> [ (<em class="replaceable"><code>column</code></em> [, ...] ) ] ]</pre>
</div>
<div class="refsect1" lang="en">
<a name="id790758"></a><h2>Description</h2>
<p> <code class="command">VACUUM</code> reclaims storage occupied by deleted tuples.
In normal <span class="productname">PostgreSQL</span> operation, tuples that
are deleted or obsoleted by an update are not physically removed from
their table; they remain present until a <code class="command">VACUUM</code> is
done. Therefore it's necessary to do <code class="command">VACUUM</code>
periodically, especially on frequently-updated tables.
</p>
<p> With no parameter, <code class="command">VACUUM</code> processes every table in the
current database. With a parameter, <code class="command">VACUUM</code> processes
only that table.
</p>
<p> <code class="command">VACUUM ANALYZE</code> performs a <code class="command">VACUUM</code>
and then an <code class="command">ANALYZE</code> for each selected table. This
is a handy combination form for routine maintenance scripts. See
<a href="sql-analyze.html">ANALYZE</a>
for more details about its processing.
</p>
<p> Plain <code class="command">VACUUM</code> (without <code class="literal">FULL</code>) simply reclaims
space and makes it
available for re-use. This form of the command can operate in parallel
with normal reading and writing of the table, as an exclusive lock
is not obtained. <code class="command">VACUUM
FULL</code> does more extensive processing, including moving of tuples
across blocks to try to compact the table to the minimum number of disk
blocks. This form is much slower and requires an exclusive lock on each
table while it is being processed.
</p>
<p> <code class="literal">FREEZE</code> is a special-purpose option that
causes tuples to be marked “<span class="quote">frozen</span>” as soon as possible,
rather than waiting until they are quite old. If this is done when there
are no other open transactions in the same database, then it is guaranteed
that all tuples in the database are “<span class="quote">frozen</span>” and will not be
subject to transaction ID wraparound problems, no matter how long the
database is left unvacuumed.
<code class="literal">FREEZE</code> is not recommended for routine use. Its only
intended usage is in connection with preparation of user-defined template
databases, or other databases that are completely read-only and will not
receive routine maintenance <code class="command">VACUUM</code> operations.
See <a href="maintenance.html" title="Chapter22.Routine Database Maintenance Tasks">Chapter22, <i>Routine Database Maintenance Tasks</i></a> for details.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id790927"></a><h2>Parameters</h2>
<div class="variablelist"><dl>
<dt><span class="term"><code class="literal">FULL</code></span></dt>
<dd><p> Selects “<span class="quote">full</span>” vacuum, which may reclaim more
space, but takes much longer and exclusively locks the table.
</p></dd>
<dt><span class="term"><code class="literal">FREEZE</code></span></dt>
<dd><p> Selects aggressive “<span class="quote">freezing</span>” of tuples.
</p></dd>
<dt><span class="term"><code class="literal">VERBOSE</code></span></dt>
<dd><p> Prints a detailed vacuum activity report for each table.
</p></dd>
<dt><span class="term"><code class="literal">ANALYZE</code></span></dt>
<dd><p> Updates statistics used by the planner to determine the most
efficient way to execute a query.
</p></dd>
<dt><span class="term"><em class="replaceable"><code>table</code></em></span></dt>
<dd><p> The name (optionally schema-qualified) of a specific table to
vacuum. Defaults to all tables in the current database.
</p></dd>
<dt><span class="term"><em class="replaceable"><code>column</code></em></span></dt>
<dd><p> The name of a specific column to analyze. Defaults to all columns.
</p></dd>
</dl></div>
</div>
<div class="refsect1" lang="en">
<a name="id791017"></a><h2>Outputs</h2>
<p> When <code class="literal">VERBOSE</code> is specified, <code class="command">VACUUM</code> emits
progress messages to indicate which table is currently being
processed. Various statistics about the tables are printed as well.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id791040"></a><h2>Notes</h2>
<p> 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
of rows, it may be a good idea to issue a <code class="command">VACUUM
ANALYZE</code> command for the affected table. This will update the
system catalogs with
the results of all recent changes, and allow the
<span class="productname">PostgreSQL</span> query planner to make better
choices in planning queries.
</p>
<p> The <code class="option">FULL</code> option is not recommended for routine use,
but may be useful in special cases. An example is when you have deleted
most of the rows in a table and would like the table to physically shrink
to occupy less disk space. <code class="command">VACUUM FULL</code> will usually
shrink the table more than a plain <code class="command">VACUUM</code> would.
</p>
<p> <code class="command">VACUUM</code> causes a substantial increase in I/O traffic,
which can cause poor performance for other active sessions. Therefore,
it is sometimes advisable to use the cost-based vacuum delay feature.
See <a href="runtime-config-resource.html#runtime-config-resource-vacuum-cost" title="17.4.4. Cost-Based Vacuum Delay
">Section17.4.4, “ Cost-Based Vacuum Delay
”</a> for details.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id791112"></a><h2>Examples</h2>
<p> The following is an example from running <code class="command">VACUUM</code> on a
table in the regression database:
</p>
<pre class="programlisting">regression=# VACUUM VERBOSE ANALYZE onek;
INFO: vacuuming "public.onek"
INFO: index "onek_unique1" now contains 1000 tuples in 14 pages
DETAIL: 3000 index tuples were removed.
0 index pages have been deleted, 0 are currently reusable.
CPU 0.01s/0.08u sec elapsed 0.18 sec.
INFO: index "onek_unique2" now contains 1000 tuples in 16 pages
DETAIL: 3000 index tuples were removed.
0 index pages have been deleted, 0 are currently reusable.
CPU 0.00s/0.07u sec elapsed 0.23 sec.
INFO: index "onek_hundred" now contains 1000 tuples in 13 pages
DETAIL: 3000 index tuples were removed.
0 index pages have been deleted, 0 are currently reusable.
CPU 0.01s/0.08u sec elapsed 0.17 sec.
INFO: index "onek_stringu1" now contains 1000 tuples in 48 pages
DETAIL: 3000 index tuples were removed.
0 index pages have been deleted, 0 are currently reusable.
CPU 0.01s/0.09u sec elapsed 0.59 sec.
INFO: "onek": removed 3000 tuples in 108 pages
DETAIL: CPU 0.01s/0.06u sec elapsed 0.07 sec.
INFO: "onek": found 3000 removable, 1000 nonremovable tuples in 143 pages
DETAIL: 0 dead tuples cannot be removed yet.
There were 0 unused item pointers.
0 pages are entirely empty.
CPU 0.07s/0.39u sec elapsed 1.56 sec.
INFO: analyzing "public.onek"
INFO: "onek": 36 pages, 1000 rows sampled, 1000 estimated total rows
VACUUM</pre>
<p>
</p>
</div>
<div class="refsect1" lang="en">
<a name="id791155"></a><h2>Compatibility</h2>
<p> There is no <code class="command">VACUUM</code> statement in the SQL standard.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id791168"></a><h2>See Also</h2>
<span class="simplelist"><a href="app-vacuumdb.html"><span class="application">vacuumdb</span></a>, <a href="runtime-config-resource.html#runtime-config-resource-vacuum-cost"> Cost-Based Vacuum Delay
</a></span>
</div>
</div></body>
</html>
|
