Commit bc63956e authored by unknown's avatar unknown

Clarified myisampack 'limitations' (note from Werner).

parent 8ede7ccc
...@@ -21192,17 +21192,17 @@ Usually, @code{myisampack} packs the datafile 40%-70%. ...@@ -21192,17 +21192,17 @@ Usually, @code{myisampack} packs the datafile 40%-70%.
MySQL uses memory mapping (@code{mmap()}) on compressed tables and MySQL uses memory mapping (@code{mmap()}) on compressed tables and
falls back to normal read/write file usage if @code{mmap()} doesn't work. falls back to normal read/write file usage if @code{mmap()} doesn't work.
There are currently two limitations with @code{myisampack}: Please note the following:
@itemize @bullet @itemize @bullet
@item @item
After packing, the table is read-only. After packing, the table is read-only. This is generally intended
(such as when accessing packed tables on a CD). Also allowing writes
to a packed table is on our TODO list but with low priority.
@item @item
@code{myisampack} can also pack @code{BLOB} or @code{TEXT} columns. The @code{myisampack} can also pack @code{BLOB} or @code{TEXT} columns.
older @code{pack_isam} could not do this. The older @code{pack_isam} (for @code{ISAM} tables) can not do this.
@end itemize @end itemize
Fixing these limitations is on our TODO list but with low priority.
@code{myisampack} is invoked like this: @code{myisampack} is invoked like this:
@example @example
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment