i have a large myisam table (about 3gb) that is updated once a day in the
middle of the night.
when it is not being updated, is there any reason not to copy it out with
rsync without shutting down the server or flush tables with read lock or
whatever?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org
Tom,
For MyISAM tables, as long as you aren't overlapping your update
cycles, I can see nothing wrong with this.
We used to rync to prepare slaves under inndb: do a broken rsync from
the live data files on the master to the archives.. when that is
complete, the result file is quite broken but significantly similar.
Lock the tables and rsync again; the second time is MUCH faster and
the result is correct.
Against a 'quieted' MyISAM table, your technique sounds fool-proof.
Of course, test your resulting tables before you commit to anything.
- michael dykman
On Thu, Dec 17, 2009 at 1:38 PM, Tom Worster
> i have a large myisam table (about 3gb) that is updated once a day in the
> middle of the night.
>
> when it is not being updated, is there any reason not to copy it out with
> rsync without shutting down the server or flush tables with read lock or
> whatever?
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: =A0 =A0http://lists.mysql.com/mysql?unsub=3Dmdykman@gmail=
..com
>
>
--=20
- michael dykman
- mdykman@gmail.com
"May you live every day of your life."
Jonathan Swift
Larry's First Law of Language Redesign: Everyone wants the colon.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg