We're trying to upgrade from 4.1.20 to 5.0.54. The problem is running
mysql_upgrade. It's turning out to be that about 70% of our tables
(over 800GB) are being needing repair.
The question is, will it be possible to "get by" without upgrading?
Eventually we'll get to it, but will data be served fr
!
On Feb 16, 2008 9:09 PM, Paul DuBois <[EMAIL PROTECTED]> wrote:
> At 9:01 PM -0600 2/16/08, Hayden Livingston wrote:
> >We're trying to upgrade from 4.1.20 to 5.0.54. The problem is running
> >mysql_upgrade. It's turning out to be that about 70% of our tables
&
t the CHECK saw as bad in the table? Rather, can we?
On Feb 16, 2008 9:24 PM, Paul DuBois <[EMAIL PROTECTED]> wrote:
> At 9:12 PM -0600 2/16/08, Hayden Livingston wrote:
> >Ahh yes, but I canceled it before all the tables/databases were
> >checked. But I guess, you're saying
I was reading the circular replication post on Onlamp.com, how they
achieve this master-master configuration. I was wondering if this will
always work out in a scenario. For example:
auto_increment_increment = 10
auto_increment_offset = 1 (for NodeA), and 2 for (NodeB)
Node1 starts at time A, 5 i
