From: | David Rowley <drowley(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Doc: Fix misleading statement about VACUUM memory limits |
Date: | 2021-08-09 04:48:59 |
Message-ID: | E1mCxDf-0001Kw-KG@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Doc: Fix misleading statement about VACUUM memory limits
In ec34040af I added a mention that there was no point in setting
maintenance_work_limit to anything higher than 1GB for vacuum, but that
was incorrect as ginInsertCleanup() also looks at what
maintenance_work_mem is set to during VACUUM and that's not limited to
1GB.
Here I attempt to make it more clear that the limitation is only around
the number of dead tuple identifiers that we can collect during VACUUM.
I've also added a note to autovacuum_work_mem to mention this limitation.
I didn't do that in ec34040af as I'd had some wrong-headed ideas about
just limiting the maximum value for that GUC to 1GB.
Author: David Rowley
Discussion: https://postgr.es/m/CAApHDvpGwOAvunp-E-bN_rbAs3hmxMoasm5pzkYDbf36h73s7w@mail.gmail.com
Backpatch-through: 9.6, same as ec34040af
Branch
------
REL_11_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/6df2971d32803c44d671d3a93fc718cb82fd7883
Modified Files
--------------
doc/src/sgml/config.sgml | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-08-09 04:49:32 | pgsql: Doc: Fix misleading statement about VACUUM memory limits |
Previous Message | David Rowley | 2021-08-09 04:48:25 | pgsql: Doc: Fix misleading statement about VACUUM memory limits |