But myisam_sort_buffer is, AFAIK, only used during Repair by sort
(in PROCESSLIST), not Repair with keycache. What did yours say
during the 21 hours? It may change from sort to keycache after awhile
-- something to do with the size of the indexes or something. Not
exactly sure about the
4) ALTER TABLE ENABLE KEYS - Puts a full load on the CPU, but neither
index nor table size seem to change, even after waiting for an hour.
Based on smaller data sets, I'd expect the index to reach something
close to 4 GB.
Update: After several hours, the index file started growing, although
-
From: Eric Jain
To: mysql-general [EMAIL PROTECTED]
Sent: Wednesday, November 05, 2003 5:11 AM
Subject: Re: LOAD DATA hangs
4) ALTER TABLE ENABLE KEYS - Puts a full load on the CPU, but
neither
index nor table size seem to change, even after waiting for an hour.
Based on smaller data sets
Any idea what has gone wrong here? Yet another limitation I have run
into?
Tried this:
1) CREATE TABLE
2) ALTER TABLE DISABLE KEYS
3) LOAD DATA - Complete after 30 min, table size 5.78 GB, index size
1.21 GB.
4) ALTER TABLE ENABLE KEYS - Puts a full load on the CPU, but neither
index nor table
I have a MyISAM table, into which I am trying to bulk-load several
gigabytes of data.
The first attempt got stuck after the table.MYD file had reached
precisely 4 GB. There wasn't any error message, but I observed that
neither the data nor the index file was increasing in size, even though
the