On Tue, Jan 14, 2003 at 04:41:53PM -0800, Ross Davis - DataAnywhere.net wrote: > > > I stand corrected. In a production environment a stopped server is as > good as crashed.
Ah, good. > I know why things work they way they do, but it would be nice to have an > option to change the replication scheme on certain databases/tables so > that things like this could occur. > > The big table on the master that I don't want at the slave is very large > and the slave only needs a bit of the data and it connects over dialup! > Replicating the whole thing would be to much bandwidth for my dialup > line. > > I will just have to be very careful. Well, you could use the "slave-skip-errors=..." syntax in your slave's my.cnf file, as described here: http://www.mysql.com/doc/en/Replication_Options.html But beware that you're knowingly asking MySQL to blow right past errors. Might that "solve" this problem for you? -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 3.23.51: up 30 days, processed 1,013,535,492 queries (379/sec. avg) --------------------------------------------------------------------- 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
