Magnus Manske wrote:
Brion Vibber wrote:
Just a heads-up for those not following CVS;
I'm fixing up an alternate
schema upgrader which will do the major schema updates and UTF-8
conversion for the 1.5 upgrade, and should be relatively friendly to
replication.
Since basically everything (cur & old) will be changed in the database,
can't we just update the master DB server *without* synchronization to
the slaves, and then set up the slaves "de novo"?
We could, but how would we benefit from this? That implies significantly
more work (reconfiguring servers to enable/disable replication on
certain databases and fanning out updates to multiple servers,
selectively disabling filesystem alterations, etc).
We could leave half of the slave servers in 1.4 format
and serve
read-only wikipedia from there, while setting up the master and the
other slaves to 1.5. Then, serve wikipedia from the 1.5 master/slaves
and setup the remaining 1.4 slaves.
If you're proposing this as an alternative to using small inserts in the
conversion script for purposes of making upgrades while the site remains
online, I don't understand how this is supposed to be equivalent.
Shouldn't take much longer, seems less complicated
and doesn't require
these fancy upgrade scripts you young people keep talking about ;.)
Sounds like it would have no benefits, be more complicated to run, and
would require yet another custom-written upgrade script to replace both
the existing stock one (which doesn't do UTF-8 conversion) *and* the one
I'm touching up (which does do the required UTF-8 conversion, and as a
side benefit does replication-friendly chunked updates).
-- brion vibber (brion @
pobox.com)