Commit2a6db5e

committed

Update out-of-date comment in vacuumlazy.c

Commit15c121b seems to haveoverlooked the need to trim this part of the comment.Pavan DeolaseeDiscussion:http://postgr.es/m/CABOikdPq_9+cWRNZ0RLKTwuZyj=uL85X=Usifa-CbPee1ZCM5A@mail.gmail.com

1 parent5dfd564 commit2a6db5eCopy full SHA for 2a6db5e

File tree

-5

lines changed

-5

lines changed

Lines changed: 4 additions & 5 deletions

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

Comments

(0)