Symlinking works fine but keep in mind an important gotcha: if you ever do
a table rebuild, mysql completely ignores your symlink and overwrites it
with the file (which may even fill up your disk).
Have you noticed these table options (from
http://dev.mysql.com/doc/mysql/en/create-table.html)?
On Sep 14, 2005, at 6:16 PM, Chris Kantarjiev wrote:
I'd like to spread the disk arm load across multiple drives. At
the moment, we mostly use MyISAM tables, but we are also
experimenting with InnoDB.
What's the 'best practice' for doing this? There's no obvious
configuration that lets me desig
Chris Kantarjiev wrote:
I'd like to spread the disk arm load across multiple drives. At
the moment, we mostly use MyISAM tables, but we are also
experimenting with InnoDB.
What's the 'best practice' for doing this? There's no obvious
configuration that lets me designate one directory for index
I'd like to spread the disk arm load across multiple drives. At
the moment, we mostly use MyISAM tables, but we are also
experimenting with InnoDB.
What's the 'best practice' for doing this? There's no obvious
configuration that lets me designate one directory for index
and another for data - am I
