{"Entry":{"collection":"relopts","key":"table-autovacuum-vacuum-cost-limit","name":"autovacuum_vacuum_cost_limit","aliases":["table.autovacuum_vacuum_cost_limit"],"metadata":{"aliases":["table.autovacuum_vacuum_cost_limit"],"category":"Tables and materialized views","content_hash":"f4643ee64ca1c2edd410bfa18a52d89da1dc5c1da19d853919fd62952cc285e3","derived_content_hash":"69d235c54a61fe4594782e800e40b199519883e90b1415fbe8966cd6712289ec","imported_at":"2026-09-30T17:44:22.218979+08:00","name":"autovacuum_vacuum_cost_limit","name_zh":"autovacuum_vacuum_cost_limit","repair_provenance":{"original_source_revision":"","receipt_sha256":"8924f035fefb51e5e0b593f43de0709a3b79d71dd37cbf9f6476dc3099a4f107","repair":"wiki-repair-20261023"},"slug":"table-autovacuum-vacuum-cost-limit","source_rev":"wiki-repair-20261023:10f490fb49737b6630bedb96663faa25e466e444c37514e384ac292fcb04156d","summary":"Per-table value for autovacuum_vacuum_cost_limit parameter."}},"Definition":{"Collection":"relopts","Key":"table-autovacuum-vacuum-cost-limit","SourceDatabase":"center","Version":"18","SourceTable":"relopt","SourceKey":"table-autovacuum-vacuum-cost-limit","SourceRevision":"eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744","Facts":{"description":["Per-table value for autovacuum_vacuum_cost_limit parameter."],"description_zh":"autovacuum_vacuum_cost_limit 参数的每表取值。","description_zh_html":"\u003cp\u003e\n\u003ca class=\"xref\" href=\"/zh/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT\"\u003eautovacuum_vacuum_cost_limit\u003c/a\u003e 参数的每表取值。\n     \u003c/p\u003e\u003ch3\u003e相关全局参数\u003c/h3\u003e\u003cp\u003e\n        指定用于自动 \u003ccode class=\"command\"\u003eVACUUM\u003c/code\u003e 操作中的代价限制值。如果指定 \u003ccode class=\"literal\"\u003e-1\u003c/code\u003e（默认值），则使用 \u003ca class=\"xref\" href=\"/zh/docs/18/runtime-config-vacuum.html#GUC-VACUUM-COST-LIMIT\"\u003evacuum_cost_limit\u003c/a\u003e 值。注意该值被按比例地分配到运行中的自动清理工作进程上（如果有多个），因此每一个工作进程的限制值之和不会超过这个变量中的值。该参数只能在 \u003ccode class=\"filename\"\u003epostgresql.conf\u003c/code\u003e 文件或在服务器命令行上设置。但是对个别表可以通过修改表存储参数来覆盖该设置。\n       \u003c/p\u003e","facts":[{"label":"Applies to","value":"Tables and materialized views"},{"label":"Value type","value":"integer"}],"related":[{"label":"Global parameter autovacuum_vacuum_cost_limit","url":"/wiki/guc/autovacuum_vacuum_cost_limit/?v=18"},{"label":"CREATE TABLE","url":"/wiki/sql/create-table/?v=18"}],"release":{"channel":"stable","label":"18.6","major":"18","ref":"Local English manual 18.6","revision":"eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"},"sections":[{"paragraphs":["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."],"title":"Scope"},{"paragraphs":["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."],"title":"Common table storage rules"},{"paragraphs":["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."],"title":"Materialized views"},{"paragraphs":["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.","Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."],"title":"Related global parameter: autovacuum_vacuum_cost_limit"}],"signature":"WITH (autovacuum_vacuum_cost_limit = value)","sources":[{"label":"PostgreSQL 18 English manual","path":"sql-createtable.html","sha256":"b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b","url":"/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT"},{"label":"Related global parameter: autovacuum_vacuum_cost_limit","path":"runtime-config-vacuum.html","sha256":"7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4","url":"/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT"},{"label":"PostgreSQL 18 English manual","path":"sql-creatematerializedview.html","sha256":"bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18","url":"/docs/18/sql-creatematerializedview.html"}],"translation_provenance":{"inputs":[{"kind":"current-pgdoc-translation","path":"/Users/vonng/pgsty/pgdoc/zh/18/html/sql-createtable.html","sha256":"c044586c69b191e0f39966b25811a0c70f12fe2bf5e7f640501e53d76ca8f775"},{"kind":"current-pgdoc-translation","path":"/Users/vonng/pgsty/pgdoc/zh/18/html/runtime-config-vacuum.html","sha256":"ea621aa6ed500fc56d21868a21fd313872cec24b86caf4c8f9bdfdc804b8235f"}],"kind":"same-version-pgdoc","locale":"zh-Hans","source_revision":"b1b500221dbe5437cfca004d6b04d3f6e422765d","version":"18"},"zh_from":"same-version-pgdoc"},"ManualEvidence":{"release":{"channel":"stable","label":"18.6","major":"18","ref":"Local English manual 18.6","revision":"eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744"},"sources":[{"label":"PostgreSQL 18 English manual","path":"sql-createtable.html","sha256":"b4d703391fe1102d0e02bd6769bef928513eb7a5542f38f7448fc77fe69e0d5b","url":"/docs/18/sql-createtable.html#RELOPTION-AUTOVACUUM-VACUUM-COST-LIMIT"},{"label":"Related global parameter: autovacuum_vacuum_cost_limit","path":"runtime-config-vacuum.html","sha256":"7047f1fa9138b97f1812532f8a905fa7479451dfd64655e029a7d387b20b22e4","url":"/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT"},{"label":"PostgreSQL 18 English manual","path":"sql-creatematerializedview.html","sha256":"bd8a6710c9f133afee191eb0ec345ef8c54bb54db2242621d8cb683c783a8b18","url":"/docs/18/sql-creatematerializedview.html"}]},"MeasuredEvidence":{}},"Text":{"Collection":"relopts","Key":"table-autovacuum-vacuum-cost-limit","SourceDatabase":"center","Version":"18","Locale":"en","Title":"autovacuum_vacuum_cost_limit","Summary":"Per-table value for autovacuum_vacuum_cost_limit parameter.","BodyHTML":"\u003cp\u003ePer-table value for autovacuum_vacuum_cost_limit parameter.\u003c/p\u003e","SourceRevision":"eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744","ContentHash":"b3f88f35436eef9d1e0f1160d5ea5328565731521595103cbf78ee4ef2efc72f","Payload":{"description":["Per-table value for autovacuum_vacuum_cost_limit parameter."],"related":[{"label":"Global parameter autovacuum_vacuum_cost_limit","url":"/wiki/guc/autovacuum_vacuum_cost_limit/?v=18"},{"label":"CREATE TABLE","url":"/wiki/sql/create-table/?v=18"}],"sections":[{"paragraphs":["This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry."],"title":"Scope"},{"paragraphs":["The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions."],"title":"Common table storage rules"},{"paragraphs":["This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information."],"title":"Materialized views"},{"paragraphs":["The following same-version GUC definition explains its purpose and units. Global defaults and activation rules describe the GUC; the relation-option override rules remain those above.","Specifies the cost limit value that will be used in automatic VACUUM operations. If -1 is specified (which is the default), the regular vacuum_cost_limit value will be used. Note that the value is distributed proportionally among the running autovacuum workers, if there is more than one, so that the sum of the limits for each worker does not exceed the value of this variable. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters."],"title":"Related global parameter: autovacuum_vacuum_cost_limit"}]}},"RequestedLocale":"en","Fallback":false,"Versions":["10","11","12","13","14","15","16","17","18","19","20"],"Locales":["en","zh-Hans"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}