{"Entry":{"collection":"guc","key":"enable_async_append","name":"enable_async_append","aliases":[],"metadata":{"baseline":false,"boot_human":"Not specified","boot_val":null,"category":"Query Tuning / Planner Method Configuration","category_zh":"","changed_in":[],"changes":[{"documentation_changed":false,"fields":{},"from":"13","status":"added","to":"14"}],"content_hash":"a91e455dd2ad910981e00a0d68449392ca3ca5a336e45bebe56a3a588fa9c110","context":"","default_changed_in":[],"default_history":[{"from":"14","to":"19","value":"on"}],"editorial":{"advice":{"olap":"Benchmark representative analytical plans with and without enable_async_append. Judge planning time, memory, spill, and execution time together; a win for one report is not evidence for a global setting.","oltp":"Keep the upstream default for routine OLTP. Use a transaction- or session-local change to diagnose whether choosing async-aware Append, which can overlap waits while reading multiple asynchronous-capable children explains a regression, then repair statistics, indexes, estimates, or query shape instead of leaving a cluster-wide method ban.","small":"Do not use enable_async_append as a permanent hint on a small host. Resource pressure may change the best method, so verify with EXPLAIN (ANALYZE, BUFFERS) and keep the change scoped to the affected workload if it is still needed."},"mechanism":["enable_async_append controls whether the planner may choose async-aware Append, which can overlap waits while reading multiple asynchronous-capable children.","It is consulted while a plan is built. A session-level change is useful for comparing EXPLAIN alternatives, but an already cached plan is not retroactively rewritten; invalidation or replanning is required to observe a different choice.","The switch changes which candidate paths the planner may cost; it does not make the chosen method faster by itself. Its user context permits session- or transaction-local changes; newly performed or newly planned work sees the value."],"pitfalls":["Treating enable_async_append as a query hint even though it affects every plan built in its scope.","Testing an already cached prepared plan and concluding that the setting has no effect.","Masking stale statistics or cardinality errors by disabling a plan method globally.","The switch changes which candidate paths the planner may cost; it does not make the chosen method faster by itself."],"references":[{"title":"PostgreSQL 19 Beta 4: enable_async_append","url":"https://www.postgresql.org/docs/19/runtime-config-query.html#GUC-ENABLE-ASYNC-APPEND"},{"title":"PostgreSQL 19 release notes","url":"https://www.postgresql.org/docs/19/release-19.html"}],"related":["enable_parallel_append","effective_io_concurrency","io_method","enable_partition_pruning"],"summary":"enable_async_append — Enables the planner's use of async append plans. Observed in PG14–19 Beta 4; its last measured boot default is on in PG19 Beta 4, with user context. This is a beta-snapshot fact and can change before PostgreSQL 19 GA."},"enumvals":[],"first_version":"14","group":"Query Tuning","group_slug":"query","imported_at":"2026-09-27T17:57:31.166797+08:00","intro_commit":{"authored_at":"2021-03-31T18:45:00+09:00","discussion":["https://postgr.es/m/CA%2BTgmoaXQEt4tZ03FtQhnzeDEMzBck%2BLrni0UWHVVgOTnA6C1w%40mail.gmail.com","https://postgr.es/m/CA%2BhUKGLBRyu0rHrDCMC4%3DRn3252gogyp1SjOgG8SEKKZv%3DFwfQ%40mail.gmail.com","https://postgr.es/m/20200228.170650.667613673625155850.horikyota.ntt%40gmail.com"],"hash":"27e1f14563cf982f1f4d71e21ef247866662a052","subject":"Add support for asynchronous execution.","url":"https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=27e1f14563cf982f1f4d71e21ef247866662a052"},"key":"enable_async_append","last_version":"20","max_val":"","min_val":"","name":"enable_async_append","position":112,"present_in":["14","15","16","17","18","19","20"],"short_desc":"Enables or disables the query planner's use of async-aware append plan types.","short_desc_zh":"","source_rev":"english-manuals:748311106858f6ce498c114208c918a2da84a3f5e5c9e414a843a7ee43767229","unit":"","vartype":"bool"}},"Definition":{"Collection":"guc","Key":"enable_async_append","SourceDatabase":"center","Version":"18","SourceTable":"guc","SourceKey":"enable_async_append","SourceRevision":"english-manuals:748311106858f6ce498c114208c918a2da84a3f5e5c9e414a843a7ee43767229","Facts":{"boot_val":"on","category":"Query Tuning / Planner Method Configuration","context":"user","description":"Enables or disables the query planner's use of async-aware append plan types. The default is on.","doc":{"anchor":"GUC-ENABLE-ASYNC-APPEND","file":"runtime-config-query.html","lang":"en","sha256":"33456ca7ef52bf28e93e34b932a411db7a1b95800179add2cf867dc6ec9144bc","slug":"18"},"documented":true,"enumvals":null,"extra_desc":null,"lang":"en","max_val":null,"metadata_version":"18","min_val":null,"name":"enable_async_append","short_desc":"Enables the planner's use of async append plans.","source":"pg-settings-source-snapshot","unit":null,"vartype":"bool"},"ManualEvidence":{"doc":{"anchor":"GUC-ENABLE-ASYNC-APPEND","file":"runtime-config-query.html","lang":"en","sha256":"33456ca7ef52bf28e93e34b932a411db7a1b95800179add2cf867dc6ec9144bc","slug":"18"}},"MeasuredEvidence":{"metadata_version":"18"}},"Text":{"Collection":"guc","Key":"enable_async_append","SourceDatabase":"center","Version":"18","Locale":"en","Title":"enable_async_append","Summary":"Enables or disables the query planner's use of async-aware append plan types. The default is on.","BodyHTML":"\u003cp\u003eEnables or disables the query planner\u0026#39;s use of async-aware append plan types. The default is on.\u003c/p\u003e","SourceRevision":"english-manuals:748311106858f6ce498c114208c918a2da84a3f5e5c9e414a843a7ee43767229","ContentHash":"a54f58b6a16e93ec9389a176a4ec8d5cc6032e325274cb3b13c025cc1449cfcf","Payload":{"description":"Enables or disables the query planner's use of async-aware append plan types. The default is on."}},"RequestedLocale":"zh-Hans","Fallback":true,"Versions":["14","15","16","17","18","19","20"],"Locales":["en"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}