lp:~tsarev/percona-server/18205_07_slave_type_conversions_error_on_truncate.patch-refactoring
- Get this branch:
- bzr branch lp:~tsarev/percona-server/18205_07_slave_type_conversions_error_on_truncate.patch-refactoring
Branch merges
Branch information
- Owner:
- Oleg Tsarev
- Status:
- Development
Recent revisions
- 217. By Oleg Tsarev
-
I renamed <name>_truncated methods to <name>, and "truncated" argument now has default value (0). I removed <name> methods, because their usage exactly correlate with new methods.
- 216. By Oleg Tsarev
-
update from lp:~tsarev/percona-server/18205_05_slave_type_conversions_error_on_truncate.patch
- 212. By Oleg Tsarev
-
Fixed code policy in wl47.patch.
Moved related tests and tests fixes from mysql-test-run.diff to wl47.patch.
Added (missed before) results for tests rpl.rpl_row_annotate_ do, rpl.rpl_ row_annotate_ dont, binlog. binlog_ row_annotate. - 208. By Oleg Tsarev
-
Return back Percona's "innodb_
stats_method= nulls_ignored" algorithm. Related Launchpad bug #892405
Related MySQL bug http://bugs.mysql. com/bug. php?id= 63320 I added new value "nulls_
ignored_ exact" for variable innodb_ stats_method. Current upsteam "nulls_ignored" algorithm calculate not_null values on every estimated (random) page, and after that try to approximates total value count.
Unfortunately, this algorithm works incorrectly on mostly null indexes (see MySQL Bug #63320).Percona'a algorithm excludes from estimation pages with nulls, calculates the count of different values and approximates total value count.
This algorithm works correctly on mostly null indexes, but has limitation - it works correctly just on one-column-key indexes. On compound-keys algorithm can works incorrectly (I didn't test this).
Unfortunately, I can't imagine now how to discard this limitation.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:percona-server/5.5