summaryrefslogtreecommitdiff
path: root/pcre/pcre16_printint.c
diff options
context:
space:
mode:
authorKristian Nielsen <knielsen@knielsen-hq.org>2016-04-07 14:44:29 +0200
committerKristian Nielsen <knielsen@knielsen-hq.org>2016-04-08 10:31:03 +0200
commit1cf852d874b0e82ebfa3854300abaacd04d3eb01 (patch)
tree1856ecfedc67ad902f5a2a741641866cf0619c1d /pcre/pcre16_printint.c
parent3f6125129f986b2d9bd4a002c30e35e6963b0e3f (diff)
downloadmariadb-git-1cf852d874b0e82ebfa3854300abaacd04d3eb01.tar.gz
MDEV-9383: Server fails to read master.info after upgrade 10.0 -> 10.1
In some cases, MariaDB 10.0 could write a master.info file that was read incorrectly by 10.1 and could cause server to fail to start after an upgrade. (If writing a new master.info file that is shorter than the old, extra junk may remain at the end of the file. This is handled properly in 10.1 with an END_MARKER line, but this line is not written by 10.0. The fix here is to make 10.1 robust at reading the master.info files written by 10.0). Fix several things around reading master.info and read_mi_key_from_file(): - read_mi_key_from_file() did not distinguish between a line with and without an eqals '=' sign. - If a line was empty, read_mi_key_from_file() would incorrectly return the key from the previous call. - An extra using_gtid=X line left-over by MariaDB 10.0 might incorrectly be read and overwrite the correct value. - Fix incorrect usage of strncmp() which should be strcmp(). - Add test cases.
Diffstat (limited to 'pcre/pcre16_printint.c')
0 files changed, 0 insertions, 0 deletions