Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commita459e58

Browse files
committed
Doc: mention executor memory usage for enable_partitionwise* GUCs
Prior to this commit, the docs for enable_partitionwise_aggregate andenable_partitionwise_join mentioned the additional overheads enablingthese causes for the query planner, but they mentioned nothing about thepossible surge in work_mem-consuming executor nodes that could end up inthe final plan. Dimitrios reported the OOM killer intervened on hisquery as a result of using enable_partitionwise_aggregate=on.Here we adjust the docs to mention the possible increase in the number ofwork_mem-consuming executor nodes that can appear in the final plan as aresult of enabling these GUCs.Reported-by: Dimitrios ApostolouReviewed-by: Ashutosh BapatDiscussion:https://postgr.es/m/3603c380-d094-136e-e333-610914fb3e80%40gmx.netDiscussion:https://postgr.es/m/CAApHDvoZ0_yqwPFEpb6h261L76BUpmh5GxBQq0LeRzQ5Jh3zzg@mail.gmail.comBackpatch-through: 12, oldest supported version
1 parent403cbd2 commita459e58

File tree

1 file changed

+14
-6
lines changed

1 file changed

+14
-6
lines changed

‎doc/src/sgml/config.sgml

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5374,9 +5374,13 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
53745374
joining the matching partitions. Partitionwise join currently applies
53755375
only when the join conditions include all the partition keys, which
53765376
must be of the same data type and have one-to-one matching sets of
5377-
child partitions. Because partitionwise join planning can use
5378-
significantly more CPU time and memory during planning, the default is
5379-
<literal>off</literal>.
5377+
child partitions. With this setting enabled, the number of nodes
5378+
whose memory usage is restricted by <varname>work_mem</varname>
5379+
appearing in the final plan can increase linearly according to the
5380+
number of partitions being scanned. This can result in a large
5381+
increase in overall memory consumption during the execution of the
5382+
query. Query planning also becomes significantly more expensive in
5383+
terms of memory and CPU. The default value is <literal>off</literal>.
53805384
</para>
53815385
</listitem>
53825386
</varlistentry>
@@ -5394,9 +5398,13 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
53945398
tables to be performed separately for each partition. If the
53955399
<literal>GROUP BY</literal> clause does not include the partition
53965400
keys, only partial aggregation can be performed on a per-partition
5397-
basis, and finalization must be performed later. Because
5398-
partitionwise grouping or aggregation can use significantly more CPU
5399-
time and memory during planning, the default is
5401+
basis, and finalization must be performed later. With this setting
5402+
enabled, the number of nodes whose memory usage is restricted by
5403+
<varname>work_mem</varname> appearing in the final plan can increase
5404+
linearly according to the number of partitions being scanned. This
5405+
can result in a large increase in overall memory consumption during
5406+
the execution of the query. Query planning also becomes significantly
5407+
more expensive in terms of memory and CPU. The default value is
54005408
<literal>off</literal>.
54015409
</para>
54025410
</listitem>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp