At 09:17 PM 1/12/2009, you wrote:
>> Why would delay_key_writes require a table rebuild? It's not
>> modifying the data. Reloading tens of millions of rows for several
>> hours seems to be a waste of time.
It probably flips a bit in the .frm file or something like that, but I
have not investigat
>> Why would delay_key_writes require a table rebuild? It's not
>> modifying the data. Reloading tens of millions of rows for several
>> hours seems to be a waste of time.
It probably flips a bit in the .frm file or something like that, but I
have not investigated it myself.
My guess is that you
In the last episode (Jan 12), mos said:
> At 12:14 PM 1/12/2009, Dan Nelson wrote:
> >In the last episode (Jan 12), mos said:
> > > I'm using MySQL 5.1 and if I execute:
> > >
> > > alter table mytable delay_key_write=1;
> > >
> > > it takes about an hour to rebuild the table. Why? As far as I
> >
At 12:14 PM 1/12/2009, Dan Nelson wrote:
In the last episode (Jan 12), mos said:
> I'm using MySQL 5.1 and if I execute:
>
> alter table mytable delay_key_write=1;
>
> it takes about an hour to rebuild the table. Why? As far as I know it
> is not changing the table structure. So why does it have
In the last episode (Jan 12), mos said:
> I'm using MySQL 5.1 and if I execute:
>
> alter table mytable delay_key_write=1;
>
> it takes about an hour to rebuild the table. Why? As far as I know it
> is not changing the table structure. So why does it have to make a
> copy of the table and reload
I'm using MySQL 5.1 and if I execute:
alter table mytable delay_key_write=1;
it takes about an hour to rebuild the table. Why? As far as I know it is
not changing the table structure. So why does it have to make a copy of the
table and reload all the data?
TIA
Mike
--
MySQL General Mailing
