Commit9a59ff4

committed

doc: clarify the effect of concurrent work_mem allocations

1 parentcc06762 commit9a59ff4Copy full SHA for 9a59ff4

File tree

-3

lines changed

-3

lines changed

Lines changed: 4 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -1697,9 +1697,10 @@ include_dir 'conf.d'`
`1697`	`1697`	`(such as a sort or hash table) before writing to temporary disk files.`
`1698`	`1698`	`If this value is specified without units, it is taken as kilobytes.`
`1699`	`1699`	`The default value is four megabytes (<literal>4MB</literal>).`
`1700`		`- Note that for a complex query, several sort or hash operations might be`
`1701`		`- running in parallel; each operation will be allowed to use as much memory`
`1702`		`- as this value specifies before it starts to write data into temporary`
	`1700`	`+ Note that a complex query might perform several sort and hash`
	`1701`	`+ operations at the same time, with each operation generally being`
	`1702`	`+ allowed to use as much memory as this value specifies before it`
	`1703`	`+ starts to write data into temporary`
`1703`	`1704`	`files. Also, several running sessions could be doing such operations`
`1704`	`1705`	`concurrently. Therefore, the total memory used could be many`
`1705`	`1706`	`times the value of <varname>work_mem</varname>; it is necessary to`

Comments

(0)