pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC

From: David Rowley <drowley(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC
Date: 2024-07-31 13:28:10
Message-ID: E1sZ9NC-0022L6-Qr@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/51895d08b41a5e5ed7e7a477fb5aa36213347ea7

Modified Files
--------------
doc/src/sgml/config.sgml | 20 ++++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2024-07-31 13:28:41 pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC
Previous Message David Rowley 2024-07-31 13:27:44 pgsql: Doc: mention executor memory usage for enable_partitionwise* GUC