{"Entry":{"collection":"guc","key":"autovacuum_analyze_scale_factor","name":"autovacuum_analyze_scale_factor","aliases":[],"metadata":{"baseline":false,"boot_human":"Not specified","boot_val":null,"category":"Vacuuming / Automatic Vacuuming","category_zh":"","changed_in":["9.2","18"],"changes":[{"documentation_changed":false,"fields":{},"from":"8.0","status":"added","to":"8.1"},{"documentation_changed":true,"fields":{},"from":"8.1","status":"changed","to":"8.2"},{"documentation_changed":true,"fields":{},"from":"8.3","status":"changed","to":"8.4"},{"documentation_changed":false,"fields":{"short_desc":{"from":"Number of tuple inserts, updates or deletes prior to analyze as a fraction of reltuples.","to":"Number of tuple inserts, updates, or deletes prior to analyze as a fraction of reltuples."}},"from":"9.1","status":"changed","to":"9.2"},{"documentation_changed":true,"fields":{},"from":"9.4","status":"changed","to":"9.5"},{"documentation_changed":false,"fields":{"category":{"from":"Autovacuum","to":"Vacuuming / Automatic Vacuuming"}},"from":"17","status":"changed","to":"18"}],"content_hash":"a0b7c436cf4fffb3766c0c32fce8d18e84613884741636aee82bd21d21fcd757","context":"","default_changed_in":[],"default_history":[{"from":"9.0","to":"19","value":"0.1"}],"derived_content_hash":"ed9ef27c6542e5735aadf2519d1c761f1f252dc701d1f335545c17bb48b2dcd1","documentation_refresh":{"batch":"20261113","original_source_rev":"wiki-repair-20261023:0944df4d68b2283e68f62581218f48e0f35d49c00ab393200c4849db2d0ac5fd","versions":{"14":"14.25","15":"15.20","16":"16.16","17":"17.12","18":"18.7","19":"19rc2"}},"editorial":{"advice":{"olap":"Run explicit ANALYZE/VACUUM after bulk loads instead of waiting only for proportional triggers; plan freezing and visibility-map advancement separately for append-only partitions.","oltp":"Tune autovacuum_analyze_scale_factor from table size, change rate, and maintenance SLA, using per-table thresholds for large/hot relations. Observe trigger intervals, dead tuples, and ANALYZE/VACUUM duration.","small":"Start with upstream. Fixed thresholds dominate on small tables; after changes, confirm worker and I/O headroom."},"mechanism":["Number of tuple inserts, updates, or deletes prior to analyze as a fraction of reltuples. A configuration reload applies a new value; existing work already in flight is not retroactively changed.","The automatic-ANALYZE trigger is autovacuum_analyze_threshold plus autovacuum_analyze_scale_factor times pg_class.reltuples; inserts, updates, and deletes feed the cumulative counter. Per-table storage parameters can override the global values, and the statistics are eventually consistent estimates.","Monitor and change autovacuum_analyze_scale_factor together with autovacuum_analyze_threshold, default_statistics_target, track_counts. Validate on the relevant server role and real workload, then use its sighup context to choose session change, reload, or restart; a historical boot default is not the current effective value."],"pitfalls":["Changing the global value while a table storage parameter overrides it.","Treating reltuples and cumulative change statistics as exact real-time counts.","Blaming a threshold without checking long transactions, replication slots, and worker saturation.","Buying short-term quiet by deferring maintenance until wraparound failsafe activates."],"references":[{"title":"PostgreSQL 19 Beta 4: autovacuum_analyze_scale_factor","url":"https://www.postgresql.org/docs/19/runtime-config-vacuum.html#GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR"},{"title":"PostgreSQL 19 release notes","url":"https://www.postgresql.org/docs/19/release-19.html"}],"related":["autovacuum_analyze_threshold","default_statistics_target","track_counts","autovacuum","autovacuum_freeze_max_age","autovacuum_max_workers"],"summary":"autovacuum_analyze_scale_factor — Number of tuple inserts, updates, or deletes prior to analyze as a fraction of reltuples. Observed in PG9.0–19 Beta 4; its last measured boot default is 0.1 in PG19 Beta 4, with sighup context. This is a beta-snapshot fact and can change before PostgreSQL 19 GA."},"enumvals":[],"first_version":"8.1","group":"Vacuuming","group_slug":"vacuum","imported_at":"2026-09-27T17:57:30.785019+08:00","intro_commit":{},"key":"autovacuum_analyze_scale_factor","last_version":"20","max_val":"","min_val":"","name":"autovacuum_analyze_scale_factor","position":17,"present_in":["8.1","8.2","8.3","8.4","9.0","9.1","9.2","9.3","9.4","9.5","9.6","10","11","12","13","14","15","16","17","18","19","20"],"repair_provenance":{"original_source_revision":"english-manuals:d982eb58ee01e6bca7cfc1e4ab5de85120dc1237f2f9322340620e59d2feb7ca","receipt_sha256":"9da0fbb736eeb84d647dbbd4ca5e5a86708b82c93b278e40b0d043cff51fa469","repair":"wiki-repair-20261023"},"short_desc":"Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE.","short_desc_zh":"","source_rev":"wiki-repair-20261023:0944df4d68b2283e68f62581218f48e0f35d49c00ab393200c4849db2d0ac5fd","unit":"","vartype":"real"}},"Definition":{"Collection":"guc","Key":"autovacuum_analyze_scale_factor","SourceDatabase":"center","Version":"18","SourceTable":"guc","SourceKey":"autovacuum_analyze_scale_factor","SourceRevision":"wiki-repair-20261023:0944df4d68b2283e68f62581218f48e0f35d49c00ab393200c4849db2d0ac5fd","Facts":{"boot_val":"0.1","category":"Vacuuming / Automatic Vacuuming","context":"sighup","description":"Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE. The default is 0.1 (10% of table size). 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.","description_zh":"指定一个表尺寸的分数，在决定是否触发 ANALYZE 时将它加到 autovacuum_analyze_threshold 上。默认值为 0.1（表尺寸的 10%）。该参数只能在 postgresql.conf 文件或在服务器命令行上设置。但是对个别表可以通过修改表存储参数来覆盖该设置。","description_zh_html":"\u003cp\u003e\n        指定一个表尺寸的分数，在决定是否触发 \u003ccode class=\"command\"\u003eANALYZE\u003c/code\u003e 时将它加到 \u003ccode class=\"varname\"\u003eautovacuum_analyze_threshold\u003c/code\u003e 上。默认值为 \u003ccode class=\"literal\"\u003e0.1\u003c/code\u003e（表尺寸的 10%）。该参数只能在 \u003ccode class=\"filename\"\u003epostgresql.conf\u003c/code\u003e 文件或在服务器命令行上设置。但是对个别表可以通过修改表存储参数来覆盖该设置。\n       \u003c/p\u003e","doc":{"anchor":"GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR","file":"runtime-config-vacuum.html","lang":"en","sha256":"599d3819c5fa60f160ba633df604ee9afd85549ffad2ae2fb0c3132a00d47417","slug":"18"},"doc_html":"\u003cp\u003e\n         Specifies a fraction of the table size to add to\n         \u003ccode class=\"varname\"\u003eautovacuum_analyze_threshold\u003c/code\u003e\n         when deciding whether to trigger an \u003ccode class=\"command\"\u003eANALYZE\u003c/code\u003e.\n         The default is \u003ccode class=\"literal\"\u003e0.1\u003c/code\u003e (10% of table size).\n         This parameter can only be set in the \u003ccode class=\"filename\"\u003epostgresql.conf\u003c/code\u003e\n         file or on the server command line;\n         but the setting can be overridden for individual tables by\n         changing table storage parameters.\n        \u003c/p\u003e","doc_same_as":"","documentation_revision":{"inputs":[{"file":"runtime-config-vacuum.html","kind":"same-version-reviewed-manual","locale":"en","sha256":"599d3819c5fa60f160ba633df604ee9afd85549ffad2ae2fb0c3132a00d47417","version":"18.7"},{"file":"runtime-config-vacuum.html","kind":"same-version-reviewed-manual","locale":"zh-Hans","sha256":"b835e4b6c446cfdaf673750aba29ba28fc55ef6cc0c531558c1e394fdc05a140","version":"18.7"}],"release":"18.7","runtime_remeasured":false,"source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552"},"documented":true,"enumvals":null,"extra_desc":null,"lang":"en","max_val":"100","metadata_version":"18","min_val":"0","name":"autovacuum_analyze_scale_factor","short_desc":"Number of tuple inserts, updates, or deletes prior to analyze as a fraction of reltuples.","source":"pg-settings-source-snapshot","translation_provenance":{"inputs":[{"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"},"unit":null,"vartype":"real","zh_from":"same-version-manual"},"ManualEvidence":{"doc":{"anchor":"GUC-AUTOVACUUM-ANALYZE-SCALE-FACTOR","file":"runtime-config-vacuum.html","lang":"en","sha256":"599d3819c5fa60f160ba633df604ee9afd85549ffad2ae2fb0c3132a00d47417","slug":"18"}},"MeasuredEvidence":{"metadata_version":"18"}},"Text":{"Collection":"guc","Key":"autovacuum_analyze_scale_factor","SourceDatabase":"center","Version":"18","Locale":"en","Title":"autovacuum_analyze_scale_factor","Summary":"Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE. The default is 0.1 (10% of table size). 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.","BodyHTML":"\u003cp\u003e\n         Specifies a fraction of the table size to add to\n         \u003ccode\u003eautovacuum_analyze_threshold\u003c/code\u003e\n         when deciding whether to trigger an \u003ccode\u003eANALYZE\u003c/code\u003e.\n         The default is \u003ccode\u003e0.1\u003c/code\u003e (10% of table size).\n         This parameter can only be set in the \u003ccode\u003epostgresql.conf\u003c/code\u003e\n         file or on the server command line;\n         but the setting can be overridden for individual tables by\n         changing table storage parameters.\n        \u003c/p\u003e","SourceRevision":"wiki-repair-20261023:0944df4d68b2283e68f62581218f48e0f35d49c00ab393200c4849db2d0ac5fd","ContentHash":"a2c0bed8adea887e51c0f89418534ea143dda7e1ec8498cc5374867e31e03d1b","Payload":{"description":"Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE. The default is 0.1 (10% of table size). 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."}},"RequestedLocale":"en","Fallback":false,"Versions":["10","11","12","13","14","15","16","17","18","19","20","8.1","8.2","8.3","8.4","9.0","9.1","9.2","9.3","9.4","9.5","9.6"],"Locales":["en","zh-Hans"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}