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 01/11/17 17:43, Phil Stracchino wrote:
>
> You may want to use 2 if there are no InnoDB tables *outside of the
> MySQL schema*, because in most
...oops. That paragraph was meant to continue: "..in most cases, the
MyISAM tables inside the mysql schema change only rarely and you are
unlikely t
On 01/11/17 16:57, scar wrote:
> i have been using the script at [1] but then i noticed that the
> incremental backups were quite large and containing some MYD and MYI
> files. so i realized these were myisam databases. i read that the best
> way to backup both innodb and myisam databases was
i have been using the script at [1] but then i noticed that the
incremental backups were quite large and containing some MYD and MYI
files. so i realized these were myisam databases. i read that the best
way to backup both innodb and myisam databases was to use the mysqldump
option --lock-tab
On 11/01/17 05:16, Charles wrote:
>
> According to both the man pages and experimentation, Debian Jessie's
> mt and mtx do not support an unlock command.
Whilst other debian versions do
# mt --version
mt-st v. 1.3
default tape device: '/dev/tape'
lock (SCSI tapes) Lock the tape drive d
