A quick note. I was at the time mainly trying to switch from a one
server machine to another without downtime. It strikes me as something
that should be doable with replication. I'd really like to see the
replication process simplified to the point where you would issue some
commands from the mysql interpreter to set the master id, the log file
name, etc. Then you run the mysql interpreter connected to do the slave
and tell it to replicate the master. It cranks for a while and when its
complete, the client is up-to-date. I realize that there will probably
need to be some time when at least a table is locked, but I think this
is a case where software improvements are probably a better long-term
solution that documentation improvements.
Jeremy D. Zawodny wrote:
> On Thu, Jan 18, 2001 at 01:21:05PM -0700, Basuki Setiawan wrote:
>
>
>> So do I
>
>
>
> In their usual amazing fashion, the MySQL team responded very quickly
>
> and put the changes online only hours after I sent them a diff.
>
>
>
> Check these:
>
>
>
> http://www.mysql.com/doc/R/e/Replication_Implementation.html
>
> http://www.mysql.com/doc/R/e/Replication_HOWTO.html
>
>
>
> to see what was updated in this pass.
>
>
>
> I have plans for several more updates, but was just inspired to work
>
> on a `mysqlhotreplicate' sort of script to setup replication with
>
> minimal server down-time...
>
>
>
> Also, please pass on suggestions for improvement. Since I'm going to
>
> venture back into the docs in a few days, I can work to get them
>
> incorporated if you don't have the inclination to work up the patches
>
> yourself.
>
>
>
> Jeremy
---------------------------------------------------------------------
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
