Hi,
I am running MySQL 3.23.14-alpha for Solaris 2.6 and
am running into disk space problems with an ISAM table
I have in it. Table info:
15.8M rows of
datetime,
varchar 16,
varchar 64,
varchar 128,
varchar 64,
varchar 64,
varchar 32,
varchar 15,
varchar 32,
varchar 64.
So currently it is taking up about 2.8G of space. I am
considering converting the table into a MyISAM table
(don't know why I didn't do that in the first place,
but oh well), but am not sure how much benefit there
is for it. Also, I am worried about the amount of
downtime required to perform such an operation. Any
ideas on an estimate (in terms of number of
operations, like is this a single full-table access,
several passes, etc)?
Also, will ALTER TABLE table TYPE=MYISAM create a new
temporary table to work with and then essentially
insert all the rows into the new copy before removing
the old table? (I am well past 50% capacity on the
machine, so if so, this operation will probably fail.)
Finally, how does MySQL handle resizing database
files? Is growth linear, or are there specific quanta
or thresholds at which the table will grow (for
example, maybe the table file size will be doubled if
the table file is over 75% utilized)?
Thanks.
=====
Jeff
// Diplomacy is the art of saying 'nice doggy'
// until you can find a rock.
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
