mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-11-27 07:21:09 +08:00
doc: clarify the effect of concurrent work_mem allocations
Reported-by: Sami Imseih Discussion: https://postgr.es/m/66590882-F48C-4A25-83E3-73792CF8C51F@amazon.com Backpatch-through: 11
This commit is contained in:
parent
cc06762141
commit
9a59ff483e
@ -1697,9 +1697,10 @@ include_dir 'conf.d'
|
||||
(such as a sort or hash table) before writing to temporary disk files.
|
||||
If this value is specified without units, it is taken as kilobytes.
|
||||
The default value is four megabytes (<literal>4MB</literal>).
|
||||
Note that for a complex query, several sort or hash operations might be
|
||||
running in parallel; each operation will be allowed to use as much memory
|
||||
as this value specifies before it starts to write data into temporary
|
||||
Note that a complex query might perform several sort and hash
|
||||
operations at the same time, with each operation generally being
|
||||
allowed to use as much memory as this value specifies before it
|
||||
starts to write data into temporary
|
||||
files. Also, several running sessions could be doing such operations
|
||||
concurrently. Therefore, the total memory used could be many
|
||||
times the value of <varname>work_mem</varname>; it is necessary to
|
||||
|
Loading…
Reference in New Issue
Block a user