addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartexportfacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

The Boston MySQL Meetup Group Message Board › Is MySQL5 Production Worthy?

Is MySQL5 Production Worthy?

A former member
Post #: 8
Is MySQL5 Production Worthy? Are you using it in a production environment yet? Should I start using it's features, which will lock me in...
A former member
Post #: 17
Is MySQL5 Production Worthy? Are you using it in a production environment yet? Should I start using it's features, which will lock me in...

I am not an experienced mysql user, but my general advice is "if it is not broken, do not fix it" If what you have now is enough for your current (and projected) needs, upgrading your production DB just for the sake of upgrading it is probably not the best option. I am sure you are evaluating 5 already, so if you found a compelling reason for the upgrade, go ahead, but as long as the version you are using in your production environment covers your needs, and support, patches and bug fixes are available, I will stick with it.

The key word here is "compelling reason", an increase of performance, security or usability, among others, could be a reason good enough to justify the upgrade.

Before upgrading your production DB, do as much testing as you can.

And of course, having an upgrade plan (and a roll back plan) will make your life a lot easier.

I found this article about upgrading from 4 to 5 interesting:


Sorry for not providing any real advice or "from the trenches" report, I hope that my two cents were of any value to you.

A former member
Post #: 1
Is MySQL5 Production Worthy? Are you using it in a production environment yet? Should I start using it's features, which will lock me in...

I've been using MySQL 5.0 in a small production environment (10,000,000 rows) with somewhere on the order of 200 inserts/second. It has shown itself to be stable and crash-free, at least for recent versions.

If your databases are small, even doing a mysqldump and import into the new major version number is fairly painless; you pay little price here. But if your database is very large (say terabyte sized) you encounter some unfortunate issues. First off, doing a mysqldump and import may be inpractical; it may take days of non-stop run time. Re-using the raw, binary database files is "reasonably" supported, but may give you nightmares should you find you must revert to a prior major version numbered server.

Also, consider that MySQL 5.0 has many new features relative to 4.x; and with every new feature comes more code complexity per query and thus more possibilities for bugs. You're at greater risk with a new version; yet the enthusiasm amongst the developers to fix bugs in the current version is greater than for prior versions.

All that said, there are some memory leaks in 5.0.18 that have just been fixed in 5.0.19. And one truly nasty bug has yet to be fixed. Multi-table UPDATEs only update some of the rows! Aieee! Example:

> UPDATE foo, bar SET foo.beverage = 'Unibroue' WHERE =
Query OK, 35 rows affected (0.04 sec)
Rows matched: 35 Changed: 35 Warnings: 0

Doing a CHECK TABLE or REPAIR TABLE doesn't help. Isn't that nice? I had a bloody heart attack one afternoon chasing that one until I slumped back in my chair and realized none of my production code uses multi-table updates. Phew. As the devos say, "fixed in the next release!" smile

Oh, those of you with MySQL 5.0 who go to run that and can't reproduce it - there's a trick. It only occurs if your database files (in particular your .FRM files) were created with a version 4 server.

Powered by mvnForum

Our Sponsors

  • Technocation, Inc.

    Video camera, host video files, meetup fees. They are non-profit.

  • Oracle, Inc.

    Oracle develops the MySQL database core and offers support and training.

  • Akiban Technologies

    Has a new table grouping technology as a denormalization alternative.

  • Tokutek

    TokuDB is a drop-in replacement for InnoDB that scales MySQL®.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy