Skip to content
This repository has been archived by the owner on Mar 19, 2021. It is now read-only.

Commit

Permalink
mention the innodb_file_per_table bit
Browse files Browse the repository at this point in the history
Signed-off-by: Joerg Steffens <joerg.steffens@dass-it.de>
  • Loading branch information
sebastianlederer authored and joergsteffens committed Sep 16, 2013
1 parent 2e995ab commit 4e1e20c
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions manuals/en/main/catmaintenance.tex
Expand Up @@ -110,6 +110,7 @@ \subsection{Compacting Your MySQL Database}
It is recommended that you use the {\bf OPTIMIZE TABLE} and {\bf ANALYZE TABLE}
statements regularly. This is to make sure that all indices are up to date
and to recycle space inside the database files.
Please note that the database files are never shrunk by {\bf MySQL}.

You can do this via the {\bf mysqlcheck} command:
\footnotesize
Expand All @@ -119,9 +120,12 @@ \subsection{Compacting Your MySQL Database}
\normalsize

If you really need to shrink the database files, you need to recreate the database.
For a {\bf MySQL} database, you could write the Bareos database as an ASCII
file (bareos.sql) then reload it by doing the following:

This only works if you use per-table tablespaces by setting the {\bf innodb\_file\_per\_table} configuration option.

See
\elink{http://dev.mysql.com/doc/refman/5.5/en/innodb-multiple-tablespaces.html}
{here} for details.
\footnotesize
\begin{verbatim}
mysqldump -f --opt bareos > bareos.sql
Expand Down

0 comments on commit 4e1e20c

Please sign in to comment.