[Rt-commit] rt branch, 4.2/warn-mysql-5.6-innodb, repushed
Alex Vandiver
alexmv at bestpractical.com
Fri Mar 6 13:19:07 EST 2015
The branch 4.2/warn-mysql-5.6-innodb was deleted and repushed:
was a828ba6d34c5098b7d339645efd30338f0aa0680
now 3e8cda519830d2c2ffc22f6a831111e999938ca6
1: 83532bb ! 1: 4393822 Warn if innodb_log_file_size would limit uploads to < 5M
@@ -38,7 +38,7 @@
+
+ if ($redo_log_size / 10 < 5 * 1024 * 1024) {
+ $redo_log_size = sprintf("%.1fM",$redo_log_size/1024/1024);
-+ warn "innodb_log_file_size is set to $innodb_log_file_size; attachments can only be 10% of this value on MySQL 5.6. Consider adjusting MySQL's innodb_log_file_size setting.\n";
++ warn "innodb_log_file_size is set to $redo_log_size; attachments can only be 10% of this value on MySQL 5.6. Consider adjusting MySQL's innodb_log_file_size setting.\n";
+ }
+ }
}
2: a828ba6 ! 2: 3e8cda5 Increase the warn threshold on max_allowed_packet to 5M
@@ -18,12 +18,3 @@
$max_packet = sprintf("%.1fM", $max_packet/1024/1024);
warn "max_allowed_packet is set to $max_packet, which limits the maximum attachment or email size that RT can process. Consider adjusting MySQL's max_allowed_packet setting.\n";
}
-@@
-
- if ($redo_log_size / 10 < 5 * 1024 * 1024) {
- $redo_log_size = sprintf("%.1fM",$redo_log_size/1024/1024);
-- warn "innodb_log_file_size is set to $innodb_log_file_size; attachments can only be 10% of this value on MySQL 5.6. Consider adjusting MySQL's innodb_log_file_size setting.\n";
-+ warn "innodb_log_file_size is set to $redo_log_size; attachments can only be 10% of this value on MySQL 5.6. Consider adjusting MySQL's innodb_log_file_size setting.\n";
- }
- }
- }
More information about the rt-commit
mailing list