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

Commitaa7d0b6

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 parent587a356 commitaa7d0b6

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
@@ -1815,9 +1815,10 @@ include_dir 'conf.d'
18151815
(such as a sort or hash table) before writing to temporary disk files.
18161816
If this value is specified without units, it is taken as kilobytes.
18171817
The default value is four megabytes (<literal>4MB</literal>).
1818-
Note that for a complex query, several sort or hash operations might be
1819-
running in parallel; each operation will generally be allowed
1820-
to use as much memory as this value specifies before it starts
1818+
Note that a complex query might perform several sort and hash
1819+
operations at the same time, with each operation generally being
1820+
allowed to use as much memory as this value specifies before
1821+
it starts
18211822
to write data into temporary files. Also, several running
18221823
sessions could be doing such operations concurrently.
18231824
Therefore, the total memory used could be many times the value
@@ -1831,7 +1832,7 @@ include_dir 'conf.d'
18311832
<para>
18321833
Hash-based operations are generally more sensitive to memory
18331834
availability than equivalent sort-based operations. The
1834-
memoryavailable for hashtables is computed by multiplying
1835+
memorylimit forahashtable is computed by multiplying
18351836
<varname>work_mem</varname> by
18361837
<varname>hash_mem_multiplier</varname>. This makes it
18371838
possible for hash-based operations to use an amount of memory

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp