mirror of
https://github.com/MariaDB/server.git
synced 2025-09-02 09:41:40 +03:00
manual.texi fix a couple of index entries
This commit is contained in:
@@ -27968,7 +27968,6 @@ spreading your tables to different disk.
|
||||
The recommended way to do this, is to just symlink databases to a
|
||||
different disk and only symlink tables as a last resort.
|
||||
|
||||
@cindex databases, symbolic links
|
||||
@menu
|
||||
* Symbolic links to databases:: Using Symbolic Links for Databases
|
||||
* Symbolic links to tables:: Using Symbolic Links for Tables
|
||||
@@ -27978,6 +27977,8 @@ different disk and only symlink tables as a last resort.
|
||||
@node Symbolic links to databases, Symbolic links to tables, Symbolic links, Symbolic links
|
||||
@subsubsection Using Symbolic Links for Databases
|
||||
|
||||
@cindex databases, symbolic links
|
||||
|
||||
The way to symlink a database is to first create a directory on some
|
||||
disk where you have free space and then create a symlink to it from
|
||||
the MySQL database directory.
|
||||
@@ -28023,7 +28024,7 @@ databases on different disks. @xref{Windows symbolic links}.
|
||||
@node Symbolic links to tables, , Symbolic links to databases, Symbolic links
|
||||
@subsubsection Using Symbolic Links for Tables
|
||||
|
||||
@cindex databases, symbolic links
|
||||
@cindex tables, symbolic links
|
||||
|
||||
Before MySQL 4.0 you should not symlink tables, if you are not
|
||||
very careful with them. The problem is that if you run @code{ALTER
|
||||
|
Reference in New Issue
Block a user