Movatterモバイル変換

Selects“full” vacuum, which can reclaim more space, but takes much longer and exclusively locks the table. This method also requires extra disk space, since it writes a new copy of the table and doesn't release the old copy until the operation is complete. Usually this should only be used when a significant amount of space needs to be reclaimed from within the table.

Selects aggressive“freezing” of tuples. SpecifyingFREEZE is equivalent to performingVACUUM with thevacuum_freeze_min_age andvacuum_freeze_table_age parameters set to zero. Aggressive freezing is always performed when the table is rewritten, so this option is redundant whenFULL is specified.

Prints a detailed vacuum activity report for each table.

Updates statistics used by the planner to determine the most efficient way to execute a query.

Normally,VACUUM will skip pages based on thevisibility map. Pages where all tuples are known to be frozen can always be skipped, and those where all tuples are known to be visible to all transactions may be skipped except when performing an aggressive vacuum. Furthermore, except when performing an aggressive vacuum, some pages may be skipped in order to avoid waiting for other sessions to finish using them. This option disables all page-skipping behavior, and is intended to be used only when the contents of the visibility map are suspect, which should happen only if there is a hardware or software issue causing database corruption.

Specifies thatVACUUM should not wait for any conflicting locks to be released when beginning work on a relation: if a relation cannot be locked immediately without waiting, the relation is skipped. Note that even with this option,VACUUM may still block when opening the relation's indexes. Additionally,VACUUM ANALYZE may still block when acquiring sample rows from partitions, table inheritance children, and some types of foreign tables. Also, whileVACUUM ordinarily processes all partitions of specified partitioned tables, this option will causeVACUUM to skip all partitions if there is a conflicting lock on the partitioned table.

Normally,VACUUM will skip index vacuuming when there are very few dead tuples in the table. The cost of processing all of the table's indexes is expected to greatly exceed the benefit of removing dead index tuples when this happens. This option can be used to forceVACUUM to process indexes when there are more than zero dead tuples. The default isAUTO, which allowsVACUUM to skip index vacuuming when appropriate. IfINDEX_CLEANUP is set toON,VACUUM will conservatively remove all dead tuples from indexes. This may be useful for backwards compatibility with earlier releases ofPostgreSQL where this was the standard behavior.

INDEX_CLEANUP can also be set toOFF to forceVACUUM toalways skip index vacuuming, even when there are many dead tuples in the table. This may be useful when it is necessary to makeVACUUM run as quickly as possible to avoid imminent transaction ID wraparound (seeSection 24.1.5). However, the wraparound failsafe mechanism controlled byvacuum_failsafe_age will generally trigger automatically to avoid transaction ID wraparound failure, and should be preferred. If index cleanup is not performed regularly, performance may suffer, because as the table is modified indexes will accumulate dead tuples and the table itself will accumulate dead line pointers that cannot be removed until index cleanup is completed.

This option has no effect for tables that have no index and is ignored if theFULL option is used. It also has no effect on the transaction ID wraparound failsafe mechanism. When triggered it will skip index vacuuming, even whenINDEX_CLEANUP is set toON.

Specifies thatVACUUM should attempt to process the main relation. This is usually the desired behavior and is the default. Setting this option to false may be useful when it is only necessary to vacuum a relation's correspondingTOAST table.

Specifies thatVACUUM should attempt to process the correspondingTOAST table for each relation, if one exists. This is usually the desired behavior and is the default. Setting this option to false may be useful when it is only necessary to vacuum the main relation. This option is required when theFULL option is used.

Specifies thatVACUUM should attempt to truncate off any empty pages at the end of the table and allow the disk space for the truncated pages to be returned to the operating system. This is normally the desired behavior and is the default unless thevacuum_truncate option has been set to false for the table to be vacuumed. Setting this option to false may be useful to avoidACCESS EXCLUSIVE lock on the table that the truncation requires. This option is ignored if theFULL option is used.

Perform index vacuum and index cleanup phases ofVACUUM in parallel usinginteger background workers (for the details of each vacuum phase, please refer toTable 27.46). The number of workers used to perform the operation is equal to the number of indexes on the relation that support parallel vacuum which is limited by the number of workers specified withPARALLEL option if any which is further limited bymax_parallel_maintenance_workers. An index can participate in parallel vacuum if and only if the size of the index is more thanmin_parallel_index_scan_size. Please note that it is not guaranteed that the number of parallel workers specified ininteger will be used during execution. It is possible for a vacuum to run with fewer workers than specified, or even with no workers at all. Only one worker can be used per index. So parallel workers are launched only when there are at least2 indexes in the table. Workers for vacuum are launched before the start of each phase and exit at the end of the phase. These behaviors might change in a future release. This option can't be used with theFULL option.

Specifies thatVACUUM should skip updating the database-wide statistics about oldest unfrozen XIDs. NormallyVACUUM will update these statistics once at the end of the command. However, this can take awhile in a database with a very large number of tables, and it will accomplish nothing unless the table that had contained the oldest unfrozen XID was among those vacuumed. Moreover, if multipleVACUUM commands are issued in parallel, only one of them can update the database-wide statistics at a time. Therefore, if an application intends to issue a series of manyVACUUM commands, it can be helpful to set this option in all but the last such command; or set it in all the commands and separately issueVACUUM (ONLY_DATABASE_STATS) afterwards.

Specifies thatVACUUM should do nothing except update the database-wide statistics about oldest unfrozen XIDs. When this option is specified, thetable_and_columns list must be empty, and no other option may be enabled exceptVERBOSE.

Specifies theBuffer Access Strategy ring buffer size forVACUUM. This size is used to calculate the number of shared buffers which will be reused as part of this strategy.0 disables use of aBuffer Access Strategy. IfANALYZE is also specified, theBUFFER_USAGE_LIMIT value is used for both the vacuum and analyze stages. This option can't be used with theFULL option except ifANALYZE is also specified. When this option is not specified,VACUUM uses the value fromvacuum_buffer_usage_limit. Higher settings can allowVACUUM to run more quickly, but having too large a setting may cause too many other useful pages to be evicted from shared buffers. The minimum value is128 kB and the maximum value is16 GB.

Specifies whether the selected option should be turned on or off. You can writeTRUE,ON, or1 to enable the option, andFALSE,OFF, or0 to disable it. Theboolean value can also be omitted, in which caseTRUE is assumed.

Specifies a non-negative integer value passed to the selected option.

Specifies an amount of memory in kilobytes. Sizes may also be specified as a string containing the numerical size followed by any one of the following memory units:B (bytes),kB (kilobytes),MB (megabytes),GB (gigabytes), orTB (terabytes).

The name (optionally schema-qualified) of a specific table or materialized view to vacuum. If the specified table is a partitioned table, all of its leaf partitions are vacuumed.

The name of a specific column to analyze. Defaults to all columns. If a column list is specified,ANALYZE must also be specified.