Content-Length: 264166 | pFad | http://github.com/postgrespro/postgres/commit/ec34040af104a1d25233eccd5715863ace6cbb10

43 Doc: mention that VACUUM can't utilize over 1GB of RAM · postgrespro/postgres@ec34040 · GitHub
Skip to content

Commit ec34040

Browse files
committed
Doc: mention that VACUUM can't utilize over 1GB of RAM
Document that setting maintenance_work_mem to values over 1GB has no effect on VACUUM. Reported-by: Martín Marqués Author: Laurenz Albe Discussion: https://postgr.es/m/CABeG9LsZ2ozUMcqtqWu_-GiFKB17ih3p8wBHXcpfnHqhCnsc7A%40mail.gmail.com Backpatch-through: 9.6, oldest supported release
1 parent 63b1af9 commit ec34040

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

doc/src/sgml/config.sgml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1893,6 +1893,12 @@ include_dir 'conf.d'
18931893
too high. It may be useful to control for this by separately
18941894
setting <xref linkend="guc-autovacuum-work-mem"/>.
18951895
</para>
1896+
<para>
1897+
Additionally, <command>VACUUM</command> is only able to utilize up to
1898+
a maximum of <literal>1GB</literal> of memory, so
1899+
<varname>maintenance_work_mem</varname> values higher than this have
1900+
no effect on <command>VACUUM</command>.
1901+
</para>
18961902
</listitem>
18971903
</varlistentry>
18981904

0 commit comments

Comments
 (0)








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/postgrespro/postgres/commit/ec34040af104a1d25233eccd5715863ace6cbb10

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy