diff options
author | unknown <heikki@hundin.mysql.fi> | 2004-01-06 13:10:57 +0200 |
---|---|---|
committer | unknown <heikki@hundin.mysql.fi> | 2004-01-06 13:10:57 +0200 |
commit | 0d770c43db695281fe24c1da18cb12216b30a542 (patch) | |
tree | da6db49617c7f040ca80232d4751ddffec5fcb73 /innobase/srv/srv0start.c | |
parent | d4a7fa95eef5f9463c3fbe405ff1ae3416e3168a (diff) | |
download | mariadb-git-0d770c43db695281fe24c1da18cb12216b30a542.tar.gz |
srv0start.c:
Add comment that the insert buffer format changed between 4.0 and 4.1.1, but the undo log format did not
innobase/srv/srv0start.c:
Add comment that the insert buffer format changed between 4.0 and 4.1.1, but the undo log format did not
Diffstat (limited to 'innobase/srv/srv0start.c')
-rw-r--r-- | innobase/srv/srv0start.c | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/innobase/srv/srv0start.c b/innobase/srv/srv0start.c index 5fe66f515bc..9dd270b6e15 100644 --- a/innobase/srv/srv0start.c +++ b/innobase/srv/srv0start.c @@ -1603,6 +1603,19 @@ NetWare. */ fflush(stderr); if (trx_doublewrite_must_reset_space_ids) { + /* Actually, we did not change the undo log format between + 4.0 and 4.1.1, and we would not need to run purge to + completion. Note also that the purge algorithm in 4.1.1 + can process the the history list again even after a full + purge, because our algorithm does not cut the end of the + history list in all cases so that it would become empty + after a full purge. That mean that we may purge 4.0 type + undo log even after this phase. + + The insert buffer record format changed between 4.0 and + 4.1.1. It is essential that the insert buffer is emptied + here! */ + fprintf(stderr, "InnoDB: You are upgrading to an InnoDB version which allows multiple\n" "InnoDB: tablespaces. Wait that purge and insert buffer merge run to\n" |