Faves for this Web page

  • We inadvertently provisioned a few database machines with MyISAM instead of InnoDB, and it has been a nightmare. I strongly advice against using MyISAM -- ever.

    With MyISAM, we periodically get these incorrect "duplicate key" errors that don't go away until you run the lenghty "repair table" command that somehow fixes everything.

    Quoted: Use MyISAM when: The data isn't too critical ( "unreliable and slow, related to table size, table repair process" )
    ...
    Use InnoDB for tables when: The table will be big (100Mb+ - "For reliability and performance, we use InnoDB for almost everything at Wikipedia - we just can't afford the downtime implied by MyISAM use and check table for 400GB of data when we get a crash." )

Add a Fave for this Web page

What happens when I press Publish?
Your Fave for this Web page gets shared with the Faves community. You can access it at any time by selecting "My Faves" from the menu above.
Why do you ask for my email address?
We use your email address to create an account, so you can easily find your Fave again at a later time.
Rate It

Separate each email address with a comma.
WE DO NOT SPAM | Please read our privacy policy.

Related Content from Around Faves

mysql

VIEW ALL

linux

VIEW ALL