Bacula-users

Re: [Bacula-users] correct strategy for mysql innodb and myisam backup

2017-01-12 08:38:24
Subject: Re: [Bacula-users] correct strategy for mysql innodb and myisam backup
From: Phil Stracchino <phils AT caerllewys DOT net>
To: bacula-users AT lists.sourceforge DOT net
Date: Thu, 12 Jan 2017 08:36:53 -0500
On 01/12/17 00:22, Josip Deanovic wrote:
> On Wednesday 2017-01-11 17:43:42 Phil Stracchino wrote:
> [...]
>> The truth is, MyISAM pretty much sucks and you shouldn't be using it in
>> production any more.  Remember that MyISAM is a 20-year-old storage
>> engine, one of whose primary design criteria was that it needed to work
>> *acceptably well* on a small shared server, at a time when a "large"
>> server might have a whole 32MB of RAM.  The default sizes of some
>> individual MySQL *BUFFERS* are larger than that.
> 
> There are applications that require MyISAM and the Innodb is not an
> option at all because critical parts of the application just doesn't
> work with innodb and if the application is proprietary software you
> can't do much about it but continue to use MyISAM.
> 
> People usually ignore such cases and insist that there is absolutely
> no reason to use MyISAM.

Most applications that "require" MyISAM "require" it for no good reason,
or depend on features that have historically been supported only by
MyISAM but are now supported in InnoDB in current MySQL releases.  It
bears case-by-case examination.  One of the most common reasons to
"require" MyISAM is fulltext search, but the honest truth is that if
you're making heavy use of fulltext search in MySQL you should probably
be using an external fulltext engine such as Sphinx, SOLR, or Lucene for
it anyway.  You might be shocked to find how many proprietary
application that "require" MyISAM do so simply because "but we've always
done it that way".

The fact remains, the MyISAM storage engine is well on its way to being
removed from MySQL, and some awareness on the matter is in order.  MySQL
5.7 already allows it to be completely disabled.


-- 
  Phil Stracchino
  Babylon Communications
  phils AT caerllewys DOT net
  phil AT co.ordinate DOT org
  Landline: 603.293.8485

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users