From 86b55790fc13f33280d426df7bb9fecc64e29e13 Mon Sep 17 00:00:00 2001 From: "mkanat%bugzilla.org" <> Date: Tue, 28 Oct 2008 06:02:15 +0000 Subject: [PATCH] Bug 141951: Set the max_packet_size for attachments (and bugs_fulltext) when connecting to MySQL Patch By Max Kanat-Alexander r=LpSolit, a=mkanat --- Bugzilla/Bug.pm | 3 --- Bugzilla/Constants.pm | 3 +++ Bugzilla/DB/Mysql.pm | 18 ++++++++++++++++++ docs/en/xml/installation.xml | 32 +------------------------------- 4 files changed, 22 insertions(+), 34 deletions(-) diff --git a/Bugzilla/Bug.pm b/Bugzilla/Bug.pm index c128d693e5..6961a1c5b8 100644 --- a/Bugzilla/Bug.pm +++ b/Bugzilla/Bug.pm @@ -223,9 +223,6 @@ use constant UPDATE_COMMENT_COLUMNS => qw( # activity table. use constant MAX_LINE_LENGTH => 254; -# Used in _check_comment(). Gives the max length allowed for a comment. -use constant MAX_COMMENT_LENGTH => 65535; - use constant SPECIAL_STATUS_WORKFLOW_ACTIONS => qw( none duplicate diff --git a/Bugzilla/Constants.pm b/Bugzilla/Constants.pm index 7282800043..0aa8d74cab 100644 --- a/Bugzilla/Constants.pm +++ b/Bugzilla/Constants.pm @@ -84,6 +84,7 @@ use File::Basename; LIST_OF_BUGS COMMENT_COLS + MAX_COMMENT_LENGTH CMT_NORMAL CMT_DUPE_OF @@ -260,6 +261,8 @@ use constant LIST_OF_BUGS => 1; # The column length for displayed (and wrapped) bug comments. use constant COMMENT_COLS => 80; +# Used in _check_comment(). Gives the max length allowed for a comment. +use constant MAX_COMMENT_LENGTH => 65535; # The type of bug comments. use constant CMT_NORMAL => 0; diff --git a/Bugzilla/DB/Mysql.pm b/Bugzilla/DB/Mysql.pm index 0a85fe2642..c01fc2a270 100644 --- a/Bugzilla/DB/Mysql.pm +++ b/Bugzilla/DB/Mysql.pm @@ -48,6 +48,11 @@ use Bugzilla::Util; use Bugzilla::Error; use Bugzilla::DB::Schema::Mysql; +# This is how many comments of MAX_COMMENT_LENGTH we expect on a single bug. +# In reality, you could have a LOT more comments than this, because +# MAX_COMMENT_LENGTH is big. +use constant MAX_COMMENTS => 50; + # This module extends the DB interface via inheritance use base qw(Bugzilla::DB); @@ -90,6 +95,19 @@ sub new { } } + # The "comments" field of the bugs_fulltext table could easily exceed + # MySQL's default max_allowed_packet. Also, MySQL should never have + # a max_allowed_packet smaller than our max_attachment_size. However, + # if we've already set a max_allowed_packet in MySQL bigger than all + # of those, we should keep it. + my (undef, $current_max_allowed) = $self->selectrow_array( + q{SHOW VARIABLES LIKE 'max\_allowed\_packet'}); + my $min_max_allowed_packet = MAX_COMMENTS * MAX_COMMENT_LENGTH; + my $max_allowed_packet = max($min_max_allowed_packet, + $current_max_allowed, + Bugzilla->params->{'maxattachmentsize'}); + $self->do("SET SESSION max_allowed_packet = $max_allowed_packet"); + return $self; } diff --git a/docs/en/xml/installation.xml b/docs/en/xml/installation.xml index a57c96735b..62b3bbb34f 100644 --- a/docs/en/xml/installation.xml +++ b/docs/en/xml/installation.xml @@ -1,5 +1,5 @@ - + Installing Bugzilla @@ -787,36 +787,6 @@ -
- Allow large attachments - - - By default, MySQL will only accept packets up to 64Kb in size. - If you want to have attachments larger than this, you will need - to modify your /etc/my.cnf as below. - - - [mysqld] - # Allow packets up to 1M - max_allowed_packet=1M - - - There is also a parameter in Bugzilla called 'maxattachmentsize' - (default = 1000 Kb) that controls the maximum allowable attachment - size. Attachments larger than either the - 'max_allowed_packet' or 'maxattachmentsize' value will not be - accepted by Bugzilla. - - - - - This does not affect Big Files, attachments that are stored directly - on disk instead of in the database. Their maximum size is - controlled using the 'maxlocalattachment' parameter. - - -
-
Allow small words in full-text indexes -- 2.47.2