Movatterモバイル変換


[0]ホーム

URL:



Facebook
Postgres Pro
Facebook
Downloads
vacuumdb
Prev UpPostgres Pro Client ApplicationsHome Next

vacuumdb

vacuumdb — garbage-collect and analyze aPostgres Pro database

Synopsis

vacuumdb [connection-option...] [option...] [-t |--tabletable [(column [,...] )] ] ... [dbname]

vacuumdb [connection-option...] [option...]-a |--all

Description

vacuumdb is a utility for cleaning aPostgres Pro database.vacuumdb will also generate internal statistics used by thePostgres Pro query optimizer.

vacuumdb is a wrapper around the SQL commandVACUUM. There is no effective difference between vacuuming and analyzing databases via this utility and via other methods for accessing the server.

Options

vacuumdb accepts the following command-line arguments:

-a
--all

Vacuum all databases.

[-d]dbname
[--dbname=]dbname

Specifies the name of the database to be cleaned or analyzed, when-a/--all is not used. If this is not specified, the database name is read from the environment variablePGDATABASE. If that is not set, the user name specified for the connection is used. Thedbname can be aconnection string. If so, connection string parameters will override any conflicting command line options.

--disable-page-skipping

Disable skipping pages based on the contents of the visibility map.

Note

This option is only available for servers runningPostgres Pro 9.6 and later.

-e
--echo

Echo the commands thatvacuumdb generates and sends to the server.

-f
--full

Performfull vacuuming.

-F
--freeze

Aggressivelyfreeze tuples.

-jnjobs
--jobs=njobs

Execute the vacuum or analyze commands in parallel by runningnjobs commands simultaneously. This option reduces the time of the processing but it also increases the load on the database server.

vacuumdb will opennjobs connections to the database, so make sure yourmax_connections setting is high enough to accommodate all connections.

Note that using this mode together with the-f (FULL) option might cause deadlock failures if certain system catalogs are processed in parallel.

--min-mxid-agemxid_age

Only execute the vacuum or analyze commands on tables with a multixact ID age of at leastmxid_age. This setting is useful for prioritizing tables to process to prevent multixact ID wraparound (seeSection 23.1.5.1).

For the purposes of this option, the multixact ID age of a relation is the greatest of the ages of the main relation and its associatedTOAST table, if one exists. Since the commands issued byvacuumdb will also process theTOAST table for the relation if necessary, it does not need to be considered separately.

--min-xid-agexid_age

Only execute the vacuum or analyze commands on tables with a transaction ID age of at leastxid_age. This setting is useful for prioritizing tables to process to prevent transaction ID wraparound (seeSection 23.1.5).

For the purposes of this option, the transaction ID age of a relation is the greatest of the ages of the main relation and its associatedTOAST table, if one exists. Since the commands issued byvacuumdb will also process theTOAST table for the relation if necessary, it does not need to be considered separately.

-q
--quiet

Do not display progress messages.

--skip-locked

Skip relations that cannot be immediately locked for processing.

-ttable [ (column [,...]) ]
--table=table [ (column [,...]) ]

Clean or analyzetable only. Column names can be specified only in conjunction with the--analyze or--analyze-only options. Multiple tables can be vacuumed by writing multiple-t switches.

-v
--verbose

Print detailed information during processing.

-V
--version

Print thevacuumdb version and exit.

-z
--analyze

Also calculate statistics for use by the optimizer.

-Z
--analyze-only

Only calculate statistics for use by the optimizer (no vacuum).

--analyze-in-stages

Only calculate statistics for use by the optimizer (no vacuum), like--analyze-only. Run several (currently three) stages of analyze with different configuration settings, to produce usable statistics faster.

This option is useful to analyze a database that was newly populated from a restored dump or bypg_upgrade. This option will try to create some statistics as fast as possible, to make the database usable, and then produce full statistics in the subsequent stages.

-?
--help

Show help aboutvacuumdb command line arguments, and exit.

vacuumdb also accepts the following command-line arguments for connection parameters:

-hhost
--host=host

Specifies the host name of the machine on which the server is running. If the value begins with a slash, it is used as the directory for the Unix domain socket.

-pport
--port=port

Specifies the TCP port or local Unix domain socket file extension on which the server is listening for connections.

-Uusername
--username=username

User name to connect as.

-w
--no-password

Never issue a password prompt. If the server requires password authentication and a password is not available by other means such as a.pgpass file, the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to enter a password.

-W
--password

Forcevacuumdb to prompt for a password before connecting to a database.

This option is never essential, sincevacuumdb will automatically prompt for a password if the server demands password authentication. However,vacuumdb will waste a connection attempt finding out that the server wants a password. In some cases it is worth typing-W to avoid the extra connection attempt.

--maintenance-db=dbname

Specifies the name of the database to connect to to discover which databases should be vacuumed, when-a/--all is used. If not specified, thepostgres database will be used, or if that does not exist,template1 will be used. This can be aconnection string. If so, connection string parameters will override any conflicting command line options. Also, connection string parameters other than the database name itself will be re-used when connecting to other databases.

Environment

PGDATABASE
PGHOST
PGPORT
PGUSER

Default connection parameters

PG_COLOR

Specifies whether to use color in diagnostic messages. Possible values arealways,auto andnever.

This utility, like most otherPostgres Pro utilities, also uses the environment variables supported bylibpq (seeSection 32.14).

Diagnostics

In case of difficulty, seeVACUUM andpsql for discussions of potential problems and error messages. The database server must be running at the targeted host. Also, any default connection settings and environment variables used by thelibpq front-end library will apply.

Notes

vacuumdb might need to connect several times to thePostgres Pro server, asking for a password each time. It is convenient to have a~/.pgpass file in such cases. SeeSection 32.15 for more information.

Examples

To clean the databasetest:

$vacuumdb test

To clean and analyze for the optimizer a database namedbigdb:

$vacuumdb --analyze bigdb

To clean a single tablefoo in a database namedxyzzy, and analyze a single columnbar of the table for the optimizer:

$vacuumdb --analyze --verbose --table='foo(bar)' xyzzy

See Also

VACUUM

Prev Up Next
reindexdb Home Postgres Pro Server Applications
epubpdf
Go to Postgres Pro Standard 12
By continuing to browse this website, you agree to the use of cookies. Go toPrivacy Policy.

[8]ページ先頭

©2009-2025 Movatter.jp