Hi,
I am using your procedure on MyISAM tables now and works but RENAME does not
work with locked tables,
(anyway it is already an atomic operation)
=BARON
Try something like this:
create table new_table like old_table;
alter table new_table add
Hi Baron!
I am going to try your solution on preprod on monday.
In the meantime, using your great slow-query-log analyzer, the strategy
I thought of was similar to yours,
but using only one select that only put a READ lock on the records
because, while the table is very 'selected' also at nigh
Hi!
On Thu, Feb 19, 2009 at 2:14 PM, Claudio Nanni wrote:
> I need to add an index on a table on a production server.
> It is one 7Gb InnoDB table with single .ibd file (one_file_per_table),
> the index creation on preprod server took 40 minutes but table was smaller.
> I tried to add the index b
I need to add an index on a table on a production server.
It is one 7Gb InnoDB table with single .ibd file (one_file_per_table),
the index creation on preprod server took 40 minutes but table was smaller.
I tried to add the index but was locking all applications on production
and had to kill it.
On Thu, Sep 25, 2003 at 03:55:26PM +0100, [EMAIL PROTECTED] wrote:
>
> Yes, i did that.
> It's given me something like
>
> si 200/300
> so 300/500
>
> It's a lot, doing my system going down. But i think that the problem is that i'm
> reserving too much memory for mysql...
That's probably true a
Yes, i did that.
It's given me something like
si 200/300
so 300/500
It's a lot, doing my system going down. But i think that the problem is that i'm
reserving too much memory for mysql...
Or could exists another reason?
Thx
Alexis
Quoting Per Andreas Buer <[EMAIL PROTECTED]>:
> [EMAIL PRO
On Wed, Sep 24, 2003 at 06:15:19PM +0100, [EMAIL PROTECTED] wrote:
>
> Hi,
>
> I'm working in MySQL with innodb tables, in Linux (Red Hat 9).
> I'm creating indexes in a table with 16 million rows (it's a fact table), and it
> takes a lot of time (2/3/4 hours), because my system is always swappi
Hi,
I'm working in MySQL with innodb tables, in Linux (Red Hat 9).
I'm creating indexes in a table with 16 million rows (it's a fact table), and it
takes a lot of time (2/3/4 hours), because my system is always swapping in/out
(i think).
At the start of the creating, it's fast (because my buff