summaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorAlex Dupre <ale@FreeBSD.org>2009-10-18 10:25:19 +0000
committerAlex Dupre <ale@FreeBSD.org>2009-10-18 10:25:19 +0000
commitee4a70f69a14332c124919163eb42ac7c0ffb6bc (patch)
treee259dbec6b149e9631631a7162c30003529d78f4 /UPDATING
parentUpdate to 5.4.3 release (see UPDATING). (diff)
Add an entry for MySQL 5.4.
Notes
Notes: svn path=/head/; revision=243003
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING13
1 files changed, 13 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index d87e47b6288e..f3d4e6123a41 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,19 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20091018
+ AFFECTS: users of databases/mysql54-server
+ AUTHOR: Alex Dupre <ale@FreeBSD.org>
+
+ After the upgrade the server may fail to start due to changes in
+ the default values of innodb_log_files_in_group and
+ innodb_log_file_size, which differ from those in earlier 5.4 releases.
+ You should discard the old InnoDB log files and let MySQL 5.4.3 create
+ new ones. It is necessary to shut down your current server cleanly so
+ that no outstanding transaction information remains in the log.
+
+ See: http://dev.mysql.com/doc/refman/5.4/en/news-5-4-3.html
+
20091014
AFFECTS: users of mail/heirloom-mailx
AUTHOR: Alexander Logvinov <avl@FreeBSD.org>