| PostgreSQL 8.2.3 Documentation | ||||
|---|---|---|---|---|
| Prev | Fast Backward | Chapter 43. System Catalogs | Fast Forward | Next |
The catalog pg_autovacuum stores optional per-relation configuration parameters for the autovacuum daemon. If there is an entry here for a particular relation, the given parameters will be used for autovacuuming that table. If no entry is present, the system-wide defaults will be used. For more information about the autovacuum daemon, see Section 22.1.4.
Table 43-10. pg_autovacuum Columns
| Name | Type | References | Description |
|---|---|---|---|
| vacrelid | oid | pg_class.oid | The table this entry is for |
| enabled | bool | If false, this table is never autovacuumed | |
| vac_base_thresh | integer | Minimum number of modified tuples before vacuum | |
| vac_scale_factor | float4 | Multiplier for reltuples to add to vac_base_thresh | |
| anl_base_thresh | integer | Minimum number of modified tuples before analyze | |
| anl_scale_factor | float4 | Multiplier for reltuples to add to anl_base_thresh | |
| vac_cost_delay | integer | Custom vacuum_cost_delay parameter | |
| vac_cost_limit | integer | Custom vacuum_cost_limit parameter | |
| freeze_min_age | integer | Custom vacuum_freeze_min_age parameter | |
| freeze_max_age | integer | Custom autovacuum_freeze_max_age parameter |
The autovacuum daemon will initiate a VACUUM operation on a particular table when the number of updated or deleted tuples exceeds vac_base_thresh plus vac_scale_factor times the number of live tuples currently estimated to be in the relation. Similarly, it will initiate an ANALYZE operation when the number of inserted, updated or deleted tuples exceeds anl_base_thresh plus anl_scale_factor times the number of live tuples currently estimated to be in the relation.
Also, the autovacuum daemon will perform a VACUUM operation to prevent transaction ID wraparound if the table's pg_class.relfrozenxid field attains an age of more than freeze_max_age transactions, whether the table has been changed or not. The system will launch autovacuum to perform such VACUUMs even if autovacuum is otherwise disabled. See Section 22.1.3 for more about wraparound prevention.
Any of the numerical fields can contain -1 (or indeed any negative value) to indicate that the system-wide default should be used for this particular value. Observe that the vac_cost_delay variable inherits its default value from the autovacuum_vacuum_cost_delay configuration parameter, or from vacuum_cost_delay if the former is set to a negative value. The same applies to vac_cost_limit. Also, autovacuum will ignore attempts to set a per-table freeze_max_age larger than the system-wide setting (it can only be set smaller), and the freeze_min_age value will be limited to half the system-wide autovacuum_freeze_max_age setting.
No comments could be found for this page.
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
In order to submit a comment, you must have a community account.
* denotes required field