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

Commitc8afad9

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 parent1512fec commitc8afad9

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
@@ -1692,9 +1692,10 @@ include_dir 'conf.d'
16921692
(such as a sort or hash table) before writing to temporary disk files.
16931693
If this value is specified without units, it is taken as kilobytes.
16941694
The default value is four megabytes (<literal>4MB</literal>).
1695-
Note that for a complex query, several sort or hash operations might be
1696-
running in parallel; each operation will generally be allowed
1697-
to use as much memory as this value specifies before it starts
1695+
Note that a complex query might perform several sort and hash
1696+
operations at the same time, with each operation generally being
1697+
allowed to use as much memory as this value specifies before
1698+
it starts
16981699
to write data into temporary files. Also, several running
16991700
sessions could be doing such operations concurrently.
17001701
Therefore, the total memory used could be many times the value
@@ -1708,7 +1709,7 @@ include_dir 'conf.d'
17081709
<para>
17091710
Hash-based operations are generally more sensitive to memory
17101711
availability than equivalent sort-based operations. The
1711-
memoryavailable for hashtables is computed by multiplying
1712+
memorylimit forahashtable is computed by multiplying
17121713
<varname>work_mem</varname> by
17131714
<varname>hash_mem_multiplier</varname>. This makes it
17141715
possible for hash-based operations to use an amount of memory

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp