mirror of
https://github.com/MariaDB/server.git
synced 2025-02-01 11:31:51 +01:00
branches/zip:
White space and formatting cleanup in the ChangeLog
This commit is contained in:
parent
866adf529d
commit
520500534a
1 changed files with 17 additions and 17 deletions
34
ChangeLog
34
ChangeLog
|
@ -1,12 +1,12 @@
|
|||
2009-09-17 The InnoDB Team
|
||||
|
||||
* mysql-test/innodb-zip.result, mysql-test/innodb-zip.test:
|
||||
Make the test pass with zlib 1.2.3.3. Apparently, the definition
|
||||
Make the test pass with zlib 1.2.3.3. Apparently, the definition
|
||||
of compressBound() has changed between zlib versions, and the
|
||||
maximum record size of a table with 1K compressed page size has
|
||||
been reduced by one byte. This is an arbitrary test. In
|
||||
practical applications, for good write performance, the compressed
|
||||
page size should be chosen to be bigger than the absolute minimum.
|
||||
been reduced by one byte. This is an arbitrary test. In practical
|
||||
applications, for good write performance, the compressed page size
|
||||
should be chosen to be bigger than the absolute minimum.
|
||||
|
||||
2009-09-16 The InnoDB Team
|
||||
|
||||
|
@ -45,29 +45,29 @@
|
|||
|
||||
* row/row0merge.c:
|
||||
Fix a bug in the merge sort that can corrupt indexes in fast index
|
||||
creation. Add some consistency checks. Check that the number of
|
||||
creation. Add some consistency checks. Check that the number of
|
||||
records remains constant in every merge sort pass.
|
||||
|
||||
2009-08-27 The InnoDB Team
|
||||
|
||||
* buf/buf0buf.c, buf/buf0lru.c, buf/buf0rea.c,
|
||||
handler/ha_innodb.cc, include/buf0buf.h, include/buf0buf.ic,
|
||||
include/buf0lru.h, include/ut0ut.h, ut/ut0ut.c:
|
||||
* buf/buf0buf.c, buf/buf0lru.c, buf/buf0rea.c, handler/ha_innodb.cc,
|
||||
include/buf0buf.h, include/buf0buf.ic, include/buf0lru.h,
|
||||
include/ut0ut.h, ut/ut0ut.c:
|
||||
Make it possible to tune the buffer pool LRU eviction policy to be
|
||||
more resistant against index scans. Introduce the settable global
|
||||
more resistant against index scans. Introduce the settable global
|
||||
variables innodb_old_blocks_pct and innodb_old_blocks_time for
|
||||
controlling the buffer pool eviction policy. The parameter
|
||||
controlling the buffer pool eviction policy. The parameter
|
||||
innodb_old_blocks_pct (5..95) controls the desired amount of "old"
|
||||
blocks in the LRU list. The default is 37, corresponding to the
|
||||
old fixed ratio of 3/8. Each time a block is accessed, it will be
|
||||
blocks in the LRU list. The default is 37, corresponding to the
|
||||
old fixed ratio of 3/8. Each time a block is accessed, it will be
|
||||
moved to the "new" blocks if its first access was at least
|
||||
innodb_old_blocks_time milliseconds ago (default 0, meaning every
|
||||
block). The idea is that in index scans, blocks will be accessed
|
||||
block). The idea is that in index scans, blocks will be accessed
|
||||
a few times within innodb_old_blocks_time, and they will remain in
|
||||
the "old" section of the LRU list. Thus, when
|
||||
innodb_old_blocks_time is nonzero, blocks retrieved for one-time
|
||||
index scans will be more likely candidates for eviction than
|
||||
blocks that are accessed in random patterns.
|
||||
the "old" section of the LRU list. Thus, when innodb_old_blocks_time
|
||||
is nonzero, blocks retrieved for one-time index scans will be more
|
||||
likely candidates for eviction than blocks that are accessed in
|
||||
random patterns.
|
||||
|
||||
2009-08-26 The InnoDB Team
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue