diff options
author | bugreport%peshkin.net <> | 2005-09-28 02:16:55 +0200 |
---|---|---|
committer | bugreport%peshkin.net <> | 2005-09-28 02:16:55 +0200 |
commit | 5a135a8ef7433ccb6093116e9a106263c85996f8 (patch) | |
tree | f60414d61fcc8c03120c108d5706e24d347d6afd /Bugzilla | |
parent | b56d5f6c828c6276449bc57bb31a00cebb592036 (diff) | |
download | bugzilla-5a135a8ef7433ccb6093116e9a106263c85996f8.tar.gz bugzilla-5a135a8ef7433ccb6093116e9a106263c85996f8.tar.xz |
Bug 307602: Smooth attach_data upgrade for sites with huge attachment tables
Patch by Joel Peshkin <bugreport@peshkin.net>
r=mkanat, a=justdave
Diffstat (limited to 'Bugzilla')
-rw-r--r-- | Bugzilla/DB/Mysql.pm | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/Bugzilla/DB/Mysql.pm b/Bugzilla/DB/Mysql.pm index c3824ab9a..952d49ff9 100644 --- a/Bugzilla/DB/Mysql.pm +++ b/Bugzilla/DB/Mysql.pm @@ -490,6 +490,16 @@ sub bz_setup_database { {TYPE => 'DATETIME', NOTNULL => 1}); } + # 2005-09-24 - bugreport@peshkin.net, bug 307602 + # Make sure that default 4G table limit is overridden + my $row = $self->selectrow_hashref("SHOW TABLE STATUS LIKE 'attach_data'"); + if ($$row{'Create_options'} !~ /MAX_ROWS/i) { + print "Converting attach_data maximum size to 100G...\n"; + $self->do("ALTER TABLE attach_data + AVG_ROW_LENGTH=1000000, + MAX_ROWS=100000"); + } + } |