<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>VACUUM</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 8.3.6 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="SQL Commands"
HREF="sql-commands.html"><LINK
REL="PREVIOUS"
TITLE="UPDATE"
HREF="sql-update.html"><LINK
REL="NEXT"
TITLE="VALUES"
HREF="sql-values.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2009-02-03T04:34:16"></HEAD
><BODY
CLASS="REFENTRY"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
>PostgreSQL 8.3.6 Documentation</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-update.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-update.html"
>Fast Backward</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="sql-values.html"
>Fast Forward</A
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="sql-values.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
><A
NAME="SQL-VACUUM"
></A
>VACUUM</H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN61100"
></A
><H2
>Name</H2
>VACUUM -- garbage-collect and optionally analyze a database</DIV
><A
NAME="AEN61103"
></A
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN61105"
></A
><H2
>Synopsis</H2
><PRE
CLASS="SYNOPSIS"
>VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ <TT
CLASS="REPLACEABLE"
><I
>table</I
></TT
> ]
VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <TT
CLASS="REPLACEABLE"
><I
>table</I
></TT
> [ (<TT
CLASS="REPLACEABLE"
><I
>column</I
></TT
> [, ...] ) ] ]</PRE
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN61110"
></A
><H2
>Description</H2
><P
> <TT
CLASS="COMMAND"
>VACUUM</TT
> reclaims storage occupied by dead 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 <TT
CLASS="COMMAND"
>VACUUM</TT
> is
done. Therefore it's necessary to do <TT
CLASS="COMMAND"
>VACUUM</TT
>
periodically, especially on frequently-updated tables.
</P
><P
> With no parameter, <TT
CLASS="COMMAND"
>VACUUM</TT
> processes every table in the
current database. With a parameter, <TT
CLASS="COMMAND"
>VACUUM</TT
> processes
only that table.
</P
><P
> <TT
CLASS="COMMAND"
>VACUUM ANALYZE</TT
> performs a <TT
CLASS="COMMAND"
>VACUUM</TT
>
and then an <TT
CLASS="COMMAND"
>ANALYZE</TT
> for each selected table. This
is a handy combination form for routine maintenance scripts. See
<A
HREF="sql-analyze.html"
><I
>ANALYZE</I
></A
>
for more details about its processing.
</P
><P
> Plain <TT
CLASS="COMMAND"
>VACUUM</TT
> (without <TT
CLASS="LITERAL"
>FULL</TT
>) 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. <TT
CLASS="COMMAND"
>VACUUM
FULL</TT
> 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
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN61129"
></A
><H2
>Parameters</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="LITERAL"
>FULL</TT
></DT
><DD
><P
> Selects <SPAN
CLASS="QUOTE"
>"full"</SPAN
> vacuum, which can reclaim more
space, but takes much longer and exclusively locks the table.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>FREEZE</TT
></DT
><DD
><P
> Selects aggressive <SPAN
CLASS="QUOTE"
>"freezing"</SPAN
> of tuples.
Specifying <TT
CLASS="LITERAL"
>FREEZE</TT
> is equivalent to performing
<TT
CLASS="COMMAND"
>VACUUM</TT
> with the
<A
HREF="runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE"
>vacuum_freeze_min_age</A
> parameter
set to zero. The <TT
CLASS="LITERAL"
>FREEZE</TT
> option is deprecated and
will be removed in a future release; set the parameter instead.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>VERBOSE</TT
></DT
><DD
><P
> Prints a detailed vacuum activity report for each table. Can be used
to help determine appropriate settings for
<A
HREF="runtime-config-resource.html#GUC-MAX-FSM-PAGES"
>max_fsm_pages</A
>,
<A
HREF="runtime-config-resource.html#GUC-MAX-FSM-RELATIONS"
>max_fsm_relations</A
>, and
<A
HREF="runtime-config-query.html#GUC-DEFAULT-STATISTICS-TARGET"
>default_statistics_target</A
>.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>ANALYZE</TT
></DT
><DD
><P
> Updates statistics used by the planner to determine the most
efficient way to execute a query.
</P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>table</I
></TT
></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
><TT
CLASS="REPLACEABLE"
><I
>column</I
></TT
></DT
><DD
><P
> The name of a specific column to analyze. Defaults to all columns.
</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN61171"
></A
><H2
>Outputs</H2
><P
> When <TT
CLASS="LITERAL"
>VERBOSE</TT
> is specified, <TT
CLASS="COMMAND"
>VACUUM</TT
> 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"
><A
NAME="AEN61176"
></A
><H2
>Notes</H2
><P
> <TT
CLASS="COMMAND"
>VACUUM</TT
> cannot be executed inside a transaction block.
</P
><P
> We recommend that active production databases be
vacuumed frequently (at least nightly), in order to
remove dead rows. After adding or deleting a large number
of rows, it might be a good idea to issue a <TT
CLASS="COMMAND"
>VACUUM
ANALYZE</TT
> 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 <TT
CLASS="OPTION"
>FULL</TT
> option is not recommended for routine use,
but might be useful in special cases. An example is when you have deleted
or updated most of the rows in a table and would like the table to
physically shrink to occupy less disk space and allow faster table
scans. <TT
CLASS="COMMAND"
>VACUUM FULL</TT
> will usually shrink the table
more than a plain <TT
CLASS="COMMAND"
>VACUUM</TT
> would. The
<TT
CLASS="OPTION"
>FULL</TT
> option does not shrink indexes; a periodic
<TT
CLASS="COMMAND"
>REINDEX</TT
> is still recommended. In fact, it is often faster
to drop all indexes, <TT
CLASS="COMMAND"
>VACUUM FULL</TT
>, and recreate the indexes.
</P
><P
> <TT
CLASS="COMMAND"
>VACUUM</TT
> causes a substantial increase in I/O traffic,
which might 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"
>Section 18.4.4</A
> for details.
</P
><P
> <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> includes an <SPAN
CLASS="QUOTE"
>"autovacuum"</SPAN
>
facility which can automate routine vacuum maintenance. For more
information about automatic and manual vacuuming, see
<A
HREF="routine-vacuuming.html"
>Section 23.1</A
>.
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN61197"
></A
><H2
>Examples</H2
><P
> The following is an example from running <TT
CLASS="COMMAND"
>VACUUM</TT
> 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"
><A
NAME="AEN61202"
></A
><H2
>Compatibility</H2
><P
> There is no <TT
CLASS="COMMAND"
>VACUUM</TT
> statement in the SQL standard.
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN61206"
></A
><H2
>See Also</H2
><A
HREF="app-vacuumdb.html"
><I
><I
>vacuumdb</I
></I
></A
>, <A
HREF="runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-VACUUM-COST"
><I
>Cost-Based Vacuum Delay</I
></A
>, <A
HREF="routine-vacuuming.html#AUTOVACUUM"
><I
>The Auto-Vacuum Daemon</I
></A
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-update.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="sql-values.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>UPDATE</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="sql-commands.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>VALUES</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
distrib
>
Mandriva
>
2008.1
>
x86_64
>
media
>
main-testing
>
by-pkgid
>
bab02a23fa9f3df8d66a9a3231b50245
>
files
>
826
