Hi Keith, I understood that the backup done by f.e mysqldump would dump the create statement only for the index - not the actually data fo the index. That would make the backup option create smaller files than lets say if you copy it 1x1 on the OS command line basis f.e with cp.
This option alone could make a big difference, depending if you are using fulltext index or not. Best regards Nils Valentin Tokyo/Japan 2003年 6月 28日 土曜日 04:23、Keith C. Ivey さんは書きました: > On 27 Jun 2003 at 14:49, David Brodbeck wrote: > > FWIW, if size is a problem, mysqldump files compress quite well with > > gzip. (Lots of repeated text.) The same is true of update logs, if > > you're keeping those. > > The same is also true of the original tables (the .MYD files), so I > stand by my statement about the size difference (whichever way it > happens to go) not being a deciding factor between using mysqldump > and copying the files (with mysqlhotcopy or otherwise). > > -- > Keith C. Ivey <[EMAIL PROTECTED]> > Tobacco Documents Online > http://tobaccodocuments.org -- --- Valentin Nils Internet Technology E-Mail: [EMAIL PROTECTED] URL: http://www.knowd.co.jp Personal URL: http://www.knowd.co.jp/staff/nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
