{"capability":{"Key":"vacuum-emergency-mode","SourceKind":"yaml","SourceDatabase":"center","SourceTable":"featurematrix.yaml","SourceKey":"Vacuum \"emergency mode\"","SourceHash":"1dd22bf9a7f3ec325b894e2836fda535a25529f246a94dd41d6abbfe9997f7fd","Name":"Vacuum \"emergency mode\"","NameLocale":"en","GroupKey":"vacuum-and-maintenance","GroupName":"VACUUM and Maintenance","GroupLocale":"en","Ordinal":6,"GroupOrder":16,"Facts":{"feature":{"description":"PostgreSQL will vacuum aggressively when it detects the possibility of transaction ID wraparound. This is controlled with the [`vacuum_failsafe_age `](https://www.postgresql.org/docs/14/runtime-config-client.html#GUC-VACUUM-FAILSAFE-AGE) and [`vacuum_multixact_failsafe_age `](https://www.postgresql.org/docs/14/runtime-config-client.html#GUC-MULTIXACT-FAILSAFE-AGE) configuration parameters.","name":"Vacuum \"emergency mode\"","versions":{"14":"Yes"}},"group":"VACUUM and Maintenance","versions":{"max":18,"min":8.1}},"Cells":[{"Version":"10","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"11","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"12","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"13","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"14","State":"yes","EvidenceKind":"yaml-transition","TransitionVersion":"14","Supported":true,"Original":"Yes"},{"Version":"15","State":"yes","EvidenceKind":"yaml-transition","TransitionVersion":"14","Supported":true,"Original":"Yes"},{"Version":"16","State":"yes","EvidenceKind":"yaml-transition","TransitionVersion":"14","Supported":true,"Original":"Yes"},{"Version":"17","State":"yes","EvidenceKind":"yaml-transition","TransitionVersion":"14","Supported":true,"Original":"Yes"},{"Version":"18","State":"yes","EvidenceKind":"yaml-transition","TransitionVersion":"14","Supported":true,"Original":"Yes"},{"Version":"8.1","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"8.2","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"8.3","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"8.4","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"9.0","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"9.1","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"9.2","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"9.3","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"9.4","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"9.5","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"},{"Version":"9.6","State":"no","EvidenceKind":"yaml-default-no","TransitionVersion":"","Supported":false,"Original":"No"}],"Texts":[{"Locale":"en","Title":"Vacuum \"emergency mode\"","BodyHTML":"\u003cp\u003ePostgreSQL will vacuum aggressively when it detects the possibility of transaction ID wraparound. This is controlled with the \u003ca href=\"https://www.postgresql.org/docs/14/runtime-config-client.html#GUC-VACUUM-FAILSAFE-AGE\" rel=\"nofollow\"\u003e\u003ccode\u003evacuum_failsafe_age \u003c/code\u003e\u003c/a\u003e and \u003ca href=\"https://www.postgresql.org/docs/14/runtime-config-client.html#GUC-MULTIXACT-FAILSAFE-AGE\" rel=\"nofollow\"\u003e\u003ccode\u003evacuum_multixact_failsafe_age \u003c/code\u003e\u003c/a\u003e configuration parameters.\u003c/p\u003e\n","SourceHash":"1dd22bf9a7f3ec325b894e2836fda535a25529f246a94dd41d6abbfe9997f7fd","ContentHash":"edbaae8cdef785f62fcc4dd224f65634d7104566c000233bdd7a22118b170ba6","Payload":{"description":"PostgreSQL will vacuum aggressively when it detects the possibility of transaction ID wraparound. This is controlled with the [`vacuum_failsafe_age `](https://www.postgresql.org/docs/14/runtime-config-client.html#GUC-VACUUM-FAILSAFE-AGE) and [`vacuum_multixact_failsafe_age `](https://www.postgresql.org/docs/14/runtime-config-client.html#GUC-MULTIXACT-FAILSAFE-AGE) configuration parameters.","name":"Vacuum \"emergency mode\"","versions":{"14":"Yes"}}},{"Locale":"zh-Hans","Title":"Vacuum “紧急模式”","BodyHTML":"\u003cp\u003e当 PostgreSQL 检测到事务 ID 回卷风险时，会更激进地执行 vacuum；该行为由 \u003ccode\u003evacuum_failsafe_age\u003c/code\u003e 控制。\u003c/p\u003e\n","SourceHash":"071091951021357a5f492adb04caed6febf4d315ac2626ca027a48dd8ec01d50","ContentHash":"611970aff395160b0ff3621d0ce3c61a9a8da5bbfe8867e9ad89d4cc95134064","Payload":{"description":"当 PostgreSQL 检测到事务 ID 回卷风险时，会更激进地执行 vacuum；该行为由 `vacuum_failsafe_age` 控制。","name":"Vacuum “紧急模式”"}}],"GroupTitles":{"en":"VACUUM and Maintenance","zh-Hans":"VACUUM 与维护"},"LegacyIDs":["360"]},"observed":true,"selected_cell":{"Version":"18","State":"yes","EvidenceKind":"yaml-transition","TransitionVersion":"14","Supported":true,"Original":"Yes"},"selected_version":"18"}