aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2024-08-01 01:26:16 +1200
committerDavid Rowley <drowley@postgresql.org>2024-08-01 01:26:16 +1200
commit3256722d7b7ff64918a0e5fdf6140de355147fe6 (patch)
treefb6ef99cbb05f96d5ec700181890ee942ad4fa0b /src
parent10fdc67f81972a03eee928a3b0ae226a78243fad (diff)
downloadpostgresql-3256722d7b7ff64918a0e5fdf6140de355147fe6.tar.gz
postgresql-3256722d7b7ff64918a0e5fdf6140de355147fe6.zip
Doc: mention executor memory usage for enable_partitionwise* GUCs
Prior to this commit, the docs for enable_partitionwise_aggregate and enable_partitionwise_join mentioned the additional overheads enabling these causes for the query planner, but they mentioned nothing about the possible surge in work_mem-consuming executor nodes that could end up in the final plan. Dimitrios reported the OOM killer intervened on his query as a result of using enable_partitionwise_aggregate=on. Here we adjust the docs to mention the possible increase in the number of work_mem-consuming executor nodes that can appear in the final plan as a result of enabling these GUCs. Reported-by: Dimitrios Apostolou Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.net Discussion: https://postgr.es/m/CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.com Backpatch-through: 12, oldest supported version
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions