10000 Tags · dhanzhang/mysql · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Tags: dhanzhang/mysql

Tags

mysql-5.5.19.t2

Toggle mysql-5.5.19.t2's commit message
Twitter MySQL 5.5.19.t2

mysql-5.5.19.t1

Toggle mysql-5.5.19.t1's commit message
Twitter MySQL 5.5.19.t1

mysql-5.5.19

Toggle mysql-5.5.19's commit message
Disable innodb_corrupt_bit.test on windows, issues with

innodb_change_buffering_debug prevents creating the Dup Key scenario on
windows

--BZR--
revision-id: jimmy.yang@oracle.com-20111122150619-78fner25z50ukkv0
property-branch-nick: mysql-5.5
testament3-sha1: e2489bf9a29968243417559578b360aa84b7d87c

clone-5.5.19-build

Toggle clone-5.5.19-build's commit message
Disable innodb_corrupt_bit.test on windows, issues with

innodb_change_buffering_debug prevents creating the Dup Key scenario on
windows

--BZR--
revision-id: jimmy.yang@oracle.com-20111122150619-78fner25z50ukkv0
property-branch-nick: mysql-5.5
testament3-sha1: e2489bf9a29968243417559578b360aa84b7d87c

mysql-5.5.18

Toggle mysql-5.5.18's commit message
BUG#13337202 - REPLICATION PERFORMANCE DROP DUE TO "THE BINLOG MAY BE…

… CORRUPTED" FLOOD

In patch mysql-5.5:revno:3097.92.133, we made the gcc 4.6.1 compiler
to stop complaining about the fact that binlog_can_be_corrupted was
defined but not used. The fix consisted in checking the variable
and printing a warning message.

However, the fix caused a regression as a message was being printed
out when there was no corrupted binary log causing performance
problems and triggering users' suspicions when there was no need.

In BUG#13337202, we do not print any message and use the variable
in an "if" with an empty body to keep the compiler happy.
--BZR--
revision-id: alfranio.correia@oracle.com-20111102152818-gt8mqvrw3mlxbvdc
property-branch-nick: mysql-5.5.18-release
testament3-sha1: 18e8e61259a94c067e751a3bf711f650c1a1f2de

mysql-5.1.60

Toggle mysql-5.1.60's commit message
Patch to fix stdint.h missing from pre Solaris 10 versions.

--BZR--
revision-id: karen.langford@oracle.com-20111029180840-adealscqqt6yy41i
property-branch-nick: mysql-5.1.60-release
testament3-sha1: d7117fccdedbbebac1a8d9089b3e7f7c2043661b

clone-5.5.18-build

Toggle clone-5.5.18-build's commit message
Null merge from mysql-5.1-security.

--BZR--
revision-id: marko.makela@oracle.com-20111026092840-pzhe6mfdhxse3os9
property-branch-nick: mysql-5.5-security
testament3-sha1: b9df144a7b71af3eae8cf6cc293b2704d877f851

clone-5.1.60-build

Toggle clone-5.1.60-build's commit message
Revert revno:3452.71.32 (Bug#12612184 fix).

Bug#12612184 RACE CONDITION AFTER BTR_CUR_PESSIMISTIC_UPDATE()

The fix introduced potentially more severe crash recovery problems
than the bug causes. Revert the fix for now.
--BZR--
revision-id: marko.makela@oracle.com-20111026092357-bwkm4nphc6maqe2y
property-branch-nick: mysql-5.1-security
testament3-sha1: f7647babf91484c9c4a27a0eae70514e3f107370

mysql-5.5.17

Toggle mysql-5.5.17's commit message
Exclude NDB man pages from a source tarball,

these sources don't have any current NDB.
--BZR--
revision-id: joerg.bruehe@oracle.com-20111004102830-5lzs0odmn3kd9m8b
property-branch-nick: clone-5.5
property-file-info: ld7:file_id49:cmakelists.txt-20091108233336-m9ewbh1c209yaw0h-297:message166:This will need to be modified as soon as NDB is added
property-file-info: to the 5.5 sources,
property-file-info: then the man page exclusion should be controlled
property-file-info: by the build option also governing NDB use.4:path18:man/CMakeLists.txtee
testament3-sha1: b93ff591858cfabb2ec85b1bcaded3c764b2c3ad

clone-5.5.17-build

Toggle clone-5.5.17-build's commit message
Bug#11759349 -- Merge of patch from mysql-5.1.

--BZR--
revision-id: ashish.y.agarwal@oracle.com-20110927121431-b9xqi2inkxnm9p41
property-branch-nick: mysql-5.5
testament3-sha1: d9d6c8dad4b88bdfabd2539d33565204fd5f3eb9
0