rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-09-28 01:11:50 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update out-of-date comment in vacuumlazy.c

Browse Source 
Commit 15c121b3ed seems to have
overlooked the need to trim this part of the comment.

Pavan Deolasee

Discussion: http://postgr.es/m/CABOikdPq_9+cWRNZ0RLKTwuZyj=uL85X=Usifa-CbPee1ZCM5A@mail.gmail.com
This commit is contained in:
Robert Haas 2017-06-22 13:35:39 -04:00
parent 5dfd564b10
commit 2a6db5eba6
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/backend/commands/vacuumlazy.c
View File

@ -4,11 +4,10 @@
* Concurrent ("lazy") vacuuming. * Concurrent ("lazy") vacuuming.
* *
* *
* The major space usage for LAZY VACUUM is storage for the array of dead * The major space usage for LAZY VACUUM is storage for the array of dead tuple
* tuple TIDs, with the next biggest need being storage for per-disk-page * TIDs. We want to ensure we can vacuum even the very largest relations with
* free space info. We want to ensure we can vacuum even the very largest * finite memory space usage. To do that, we set upper bounds on the number of
* relations with finite memory space usage. To do that, we set upper bounds * tuples we will keep track of at once.
* on the number of tuples and pages we will keep track of at once.
* *
* We are willing to use at most maintenance_work_mem (or perhaps * We are willing to use at most maintenance_work_mem (or perhaps
* autovacuum_work_mem) memory space to keep track of dead tuples. We * autovacuum_work_mem) memory space to keep track of dead tuples. We