diff options
| author | David Rowley | 2021-08-09 04:46:49 +0000 |
|---|---|---|
| committer | David Rowley | 2021-08-09 04:46:49 +0000 |
| commit | b5815dd00ad32b413070b088d083754d7ec42d37 (patch) | |
| tree | 649ae12395cc7e199687cdbea5d6d73c8188eb1e /src/backend/tcop/postgres.c | |
| parent | c26552f4fc4fb72c64103ea877ea3c2a251856ad (diff) | |
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
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions