1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Adapt to WL#8845 Implement an InnoDB redo log format version identifier

Browse Source 
recv_find_max_checkpoint(): Amend the error message to give advice
about downgrading. The 5.7.9 redo log format was intentionally changed
so that older MySQL versions will not find a valid redo log checkpoint.
This commit is contained in:
Marko Mäkelä 2015-09-11 10:32:10 +03:00
parent ddcad361d6
commit adf12e6e17
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
storage/innobase/log/log0recv.c
View File

@ -1,6 +1,6 @@
/***************************************************************************** /*****************************************************************************
Copyright (c) 1997, 2010, Innobase Oy. All Rights Reserved. Copyright (c) 1997, 2015, Oracle and/or its affiliates. All Rights Reserved.
This program is free software; you can redistribute it and/or modify it under This program is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software the terms of the GNU General Public License as published by the Free Software
@ -736,6 +736,10 @@ not_consistent:
fprintf(stderr, fprintf(stderr,
"InnoDB: No valid checkpoint found.\n" "InnoDB: No valid checkpoint found.\n"
"InnoDB: If you are attempting downgrade"
" from MySQL 5.7.9 or later,\n"
"InnoDB: please refer to " REFMAN
"upgrading-downgrading.html\n"
"InnoDB: If this error appears when you are" "InnoDB: If this error appears when you are"
" creating an InnoDB database,\n" " creating an InnoDB database,\n"
"InnoDB: the problem may be that during" "InnoDB: the problem may be that during"