Bugzilla database corruption in MySQL 3.23.51
kevin.benton at amd.com
Tue Oct 18 20:24:12 UTC 2005
>From my experience with 3.23, it's uncommon to have index issues. On
the other hand, if your hard disk is having issues, anything is
possible. You may want to consider moving your database to a different
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
Personal Computing Systems Group
Advanced Micro Devices
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information. Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices. This
communication is for the intended recipient(s) only. If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.
> -----Original Message-----
> From: developers-owner at bugzilla.org
[mailto:developers-owner at bugzilla.org]
> On Behalf Of Mick Weiss
> Sent: Tuesday, October 18, 2005 10:52 AM
> To: developers at bugzilla.org
> Subject: Re: Bugzilla database corruption in MySQL 3.23.51
> Hi Eddie,
> that is a really old version of MySQL. I can imagine that this is not
> the only problem that you have. I would definitly upgrade to the
> stable (4.1 at the time of this writing).
> Best Regards,
> - Mick
> Eddie Xie wrote:
> >My Bugzilla is using an old version of MySQL ("Ver 3.23.51 for
> >pc-linux-gnu on i686") I have noticed lately an increasing number of
> >index corruption problems. Does MySQL have a reputation for this?
> >are my databases just getting to big?
> >I guess the real issue is avoiding these index corruption problems in
> >the first place. Would updrading my MySQL implementation help out
> To view or change your list settings, click here:
More information about the developers