Commit35bc0ec

committed

Note case where nbtree VACUUM finishes splits.

The nbtree README claims that VACUUM can never finish interrupted pagesplits by design. That isn't entirely accurate, though. Note anexception to the general rule.Discussion:https://postgr.es/m/CAH2-Wz=_Xvv8byzK_LvY4ci76OgsHCQzoKF7We8yG9waO7j6rA@mail.gmail.com

1 parent1638623 commit35bc0ecCopy full SHA for 35bc0ec

File tree

-1

lines changed

-1

lines changed

Lines changed: 4 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -476,7 +476,10 @@ inserting a downlink might require splitting a page, it might fail if you`
`476`	`476`	`run out of disk space. That would be bad during VACUUM - the reason for`
`477`	`477`	`running VACUUM in the first place might be that you run out of disk space,`
`478`	`478`	`and now VACUUM won't finish because you're out of disk space. In contrast,`
`479`		`-an insertion can require enlarging the physical file anyway.`
	`479`	`+an insertion can require enlarging the physical file anyway. There is one`
	`480`	`+minor exception: VACUUM finishes interrupted splits of internal pages when`
	`481`	`+deleting their children. This allows the code for re-finding parent items`
	`482`	`+to be used by both page splits and page deletion.`
`480`	`483`
`481`	`484`	`To identify missing downlinks, when a page is split, the left page is`
`482`	`485`	`flagged to indicate that the split is not yet complete (INCOMPLETE_SPLIT).`

Comments

(0)