diff options
| author | David Rowley <drowley@postgresql.org> | 2024-08-01 01:25:25 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2024-08-01 01:25:25 +1200 |
| commit | 057ee9183c2142f6ecd9035aa6b96c5509c18a27 (patch) | |
| tree | c103a565e01ab3fbfc2757c670af642ede5b9879 /src/backend/jit/llvm/llvmjit_expr.c | |
| parent | e54a42ac9d49ef9cd660d1bf55f09c88bb841ee9 (diff) | |
| download | postgresql-057ee9183c2142f6ecd9035aa6b96c5509c18a27.tar.gz postgresql-057ee9183c2142f6ecd9035aa6b96c5509c18a27.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/backend/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions