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

Commitc3f7e91

Browse files
committed
doc: clarify the effect of concurrent work_mem allocations
Reported-by: Sami ImseihDiscussion:https://postgr.es/m/66590882-F48C-4A25-83E3-73792CF8C51F@amazon.comBackpatch-through: 11
1 parent7bb0f4a commitc3f7e91

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

‎doc/src/sgml/config.sgml

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1824,9 +1824,10 @@ include_dir 'conf.d'
18241824
(such as a sort or hash table) before writing to temporary disk files.
18251825
If this value is specified without units, it is taken as kilobytes.
18261826
The default value is four megabytes (<literal>4MB</literal>).
1827-
Note that for a complex query, several sort or hash operations might be
1828-
running in parallel; each operation will generally be allowed
1829-
to use as much memory as this value specifies before it starts
1827+
Note that a complex query might perform several sort and hash
1828+
operations at the same time, with each operation generally being
1829+
allowed to use as much memory as this value specifies before
1830+
it starts
18301831
to write data into temporary files. Also, several running
18311832
sessions could be doing such operations concurrently.
18321833
Therefore, the total memory used could be many times the value
@@ -1840,7 +1841,7 @@ include_dir 'conf.d'
18401841
<para>
18411842
Hash-based operations are generally more sensitive to memory
18421843
availability than equivalent sort-based operations. The
1843-
memoryavailable for hashtables is computed by multiplying
1844+
memorylimit forahashtable is computed by multiplying
18441845
<varname>work_mem</varname> by
18451846
<varname>hash_mem_multiplier</varname>. This makes it
18461847
possible for hash-based operations to use an amount of memory

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp