PostgreSQL

  This option is only available for servers running PostgreSQL 9.6 and later.
  ====
[.term]#`+-e+` +
#[.term]#`+--echo+`#::
  Echo the commands that vacuumdb generates and sends to the server.
[.term]#`+-f+` +
#[.term]#`+--full+`#::
  Perform [.quote]#“[.quote]#full#”# vacuuming.
[.term]#`+-F+` +
#[.term]#`+--freeze+`#::
  Aggressively [.quote]#“[.quote]#freeze#”# tuples.
[.term]#`+--force-index-cleanup+`#::
  Always remove index entries pointing to dead tuples.
  +
  [NOTE]
  ====
  ==== Note

  This option is only available for servers running PostgreSQL 12 and later.
  ====
[.term]#`+-j +`_`+njobs+`_ +
#[.term]#`+--jobs=+`_`+njobs+`_#::
  Execute the vacuum or analyze commands in parallel by running _`+njobs+`_ commands simultaneously. This option may reduce the processing time but it also increases the load on the database server.
  +
  vacuumdb will open _`+njobs+`_ connections to the database, so make sure your link:runtime-config-connection.html#GUC-MAX-CONNECTIONS[max_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.
[.term]#`+--min-mxid-age +`_`+mxid_age+`_#::
  Only execute the vacuum or analyze commands on tables with a multixact ID age of at least _`+mxid_age+`_. This setting is useful for prioritizing tables to process to prevent multixact ID wraparound (see link:routine-vacuuming.html#VACUUM-FOR-MULTIXACT-WRAPAROUND[Section 25.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 associated TOAST table, if one exists. Since the commands issued by vacuumdb will also process the TOAST table for the relation if necessary, it does not need to be considered separately.
  +
  [NOTE]
  ====
  ==== Note

  This option is only available for servers running PostgreSQL 9.6 and later.
  ====
[.term]#`+--min-xid-age +`_`+xid_age+`_#::
  Only execute the vacuum or analyze commands on tables with a transaction ID age of at least _`+xid_age+`_. This setting is useful for prioritizing tables to process to prevent transaction ID wraparound (see link:routine-vacuuming.html#VACUUM-FOR-WRAPAROUND[Section 25.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 associated TOAST table, if one exists. Since the commands issued by vacuumdb will also process the TOAST table for the relation if necessary, it does not need to be considered separately.
  +
  [NOTE]
  ====
  ==== Note

  This option is only available for servers running PostgreSQL 9.6 and later.
  ====
[.term]#`+--no-index-cleanup+`#::
  Do not remove index entries pointing to dead tuples.
  +
  [NOTE]
  ====
  ==== Note

  This option is only available for servers running PostgreSQL 12 and later.
  ====
[.term]#`+--no-process-toast+`#::
  Skip the TOAST table associated with the table to vacuum, if any.
  +
  [NOTE]
  ====
  ==== Note

  This option is only available for servers running PostgreSQL 14 and later.
  ====
[.term]#`+--no-truncate+`#::
  Do not truncate empty pages at the end of the table.
  +
  [NOTE]
  ====
  ==== Note

  This option is only available for servers running PostgreSQL 12 and later.
  ====
[.term]#`+-P +`_`+parallel_workers+`_ +
#[.term]#`+--parallel=+`_`+parallel_workers+`_#::
  Specify the number of parallel workers for _parallel vacuum_. This allows the vacuum to leverage multiple CPUs to process indexes. See link:sql-vacuum.html[[.refentrytitle]#VACUUM#].
  +
  [NOTE]
  ====
  ==== Note

  This option is only available for servers running PostgreSQL 13 and later.
  ====
[.term]#`+-q+` +
#[.term]#`+--quiet+`#::
  Do not display progress messages.
[.term]#`+--skip-locked+`#::
  Skip relations that cannot be immediately locked for processing.
  +
  [NOTE]
  ====
  ==== Note

  This option is only available for servers running PostgreSQL 12 and later.
  ====
[.term]#`+-t +`_`+table+`_`+ [ (+`_`+column+`_`+ [,...]) ]+` +
#[.term]#`+--table=+`_`+table+`_`+ [ (+`_`+column+`_`+ [,...]) ]+`#::
  Clean or analyze _`+table+`_ 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.
  +
  [TIP]
  ====
  ==== Tip

  If you specify columns, you probably have to escape the parentheses from the shell. (See examples below.)
  ====
[.term]#`+-v+` +
#[.term]#`+--verbose+`#::
  Print detailed information during processing.
[.term]#`+-V+` +
#[.term]#`+--version+`#::
  Print the vacuumdb version and exit.
[.term]#`+-z+` +
#[.term]#`+--analyze+`#::
  Also calculate statistics for use by the optimizer.
[.term]#`+-Z+` +
#[.term]#`+--analyze-only+`#::
  Only calculate statistics for use by the optimizer (no vacuum).
[.term]#`+--analyze-in-stages+`#::
  Only calculate statistics for use by the optimizer (no vacuum), like `+--analyze-only+`. Run three stages of analyze; the first stage uses the lowest possible statistics target (see link:runtime-config-query.html#GUC-DEFAULT-STATISTICS-TARGET[default_statistics_target]) to produce usable statistics faster, and subsequent stages build the full statistics.
  +
  This option is only useful to analyze a database that currently has no statistics or has wholly incorrect ones, such as if it is newly populated from a restored dump or by `+pg_upgrade+`. Be aware that running with this option in a database with existing statistics may cause the query optimizer choices to become transiently worse due to the low statistics targets of the early stages.
[.term]#`+-?+` +
#[.term]#`+--help+`#::
  Show help about vacuumdb command line arguments, and exit.