]> git.ipfire.org Git - thirdparty/sqlite.git/commit
When reusing pages as part of creating a new index, allocate the leaves from each...
authordan <dan@noemail.net>
Mon, 6 Aug 2012 18:50:11 +0000 (18:50 +0000)
committerdan <dan@noemail.net>
Mon, 6 Aug 2012 18:50:11 +0000 (18:50 +0000)
commit428c218c90cce7bbff210a19ee01ecdc01511076
tree70a786e7696405b715daf18df4c858e25427a467
parent8c5287ec73659e982e593c339b92e6ea2f5ff3d1
When reusing pages as part of creating a new index, allocate the leaves from each free-list trunk page in ascending order, instead of trying to maximize localization for each individual allocation. This increases the chance that pages will be written to disk in ascending order by a large CREATE INDEX statement, improving overall performance.

FossilOrigin-Name: d045f8b2d44e388d8c4549ff02d4ca7eff4e2038
manifest
manifest.uuid
src/analyze.c
src/btree.c
src/btree.h
src/btreeInt.h
src/build.c
src/sqliteInt.h
src/test_vfs.c
src/vdbe.c
test/index5.test [new file with mode: 0644]