Admittedly, ENABLE KEYS is something new to me so I think I'll have
fun tackling this issue. I just solved a build problem in FreeBSD so
I'm going to start investigating this bug.
Cheers,
Toru
On Wed, Jun 2, 2010 at 6:20 AM, Patrick Crews <email address hidden> wrote:
> ** Changed in: drizzle
> Assignee: (unassigned) => Toru Maesaka (tmaesaka)
>
> --
> Using 'ALTER TABLE <> ENABLE KEYS' on a BlitzDB table locks up the server
> https://bugs.launchpad.net/bugs/588487
> You received this bug notification because you are a bug assignee.
>
> Status in A Lightweight SQL Database for Cloud and Web: New
>
> Bug description:
> Issuing an ALTER TABLE <name> ENABLE KEYS against a BlitzDB table causes Drizzle to lock up.
>
> Background:
> This was discovered while attempting to test BlitzDB with the Random Query Generator and part of the gendata (table creation + population script) process involves disabling/enabling keys during the initial table load.
>
> Test case:
> You will see appropriate warnings for key size being too long on the 1024 column as well as warnings for the truncation of data for the varchar_10 columns.
>
> You will also see an appropriate warning when we attempt to DISABLE KEYS (not supported).
>
> However, when we hit the ENABLE KEYS query, things lock up every time.
> drizzle> ALTER TABLE `C` ENABLE KEYS;
> Query OK, 0 rows affected, 1 warning (0 sec)
> ^ It appears that the query is processed correctly, however any queries after this point will not be productive, nor will additional attempts to connect to the server.
>
>
> CREATE TABLE `C` (
> `col_varchar_10_key` varchar(10),
> `col_varchar_10` varchar(10),
> `col_int` int,
> `col_varchar_1024_key` varchar(1024),
> `col_varchar_1024` varchar(1024),
> `col_int_key` int,
> pk integer auto_increment,
> /*Indices*/
> key (`col_varchar_10_key` ),
> key (`col_varchar_1024_key` ),
> key (`col_int_key` ),
> primary key (pk)) ENGINE=blitzdb ;
> ALTER TABLE `C` DISABLE KEYS ;
> INSERT /*! IGNORE */ INTO C VALUES ('xermmjkovqnoqhpubzfjxwqacdiwyekwemegyaluzytnccflbvqnqnmfvvlhitckzgppyilihmleccmmxqxcilxqvfikqseftdkgtlqzbwpucapktdeqxndcqytizhxaaiyashfuwbyynvenjcsmasklnxxtbzrqxmoupppjcctptgoksleizxkrbednzzwgvlnnghjvvtlpajyalhsygtjrhjxreywihgnxlevtsvfzsztftgvgzkqhwpnbztbcpoqdmhgjffokjvoae', 'from', -2114322432, 'mean', 't', -1076690944, NULL) , ('r', 'qxermmjkovqnoqhpubzfjxwqacdiwyekwemegyaluzytnccflbvqnqnmfvvlhitckzgppyilihmleccmmxqxcilxqvfikqseftdkgtlqzbwpucapktdeqxndcqytizhxaaiyashfuwbyynvenjcsmasklnxxtbzrqxmoupppjcctptgoksleizxkrbednzzwgvlnnghjvvtlpajyalhsygtjrhjxreywihgn', 0, 'his', 'eqxermmjkovqnoqhpubzfjxwqacdiwyekwemegyaluzytnccflbvqnqnmfvvlhitckzgppyilihmleccmmxqxcilxqvfikqseftdkgtlqzbwpucapktdeqxndcqytizhxaaiyashfuwbyynvenjcsmasklnxxtbzrqxmoupppjcctptgokslei', NULL, NULL) ;
> COMMIT;
> ALTER TABLE `C` ENABLE KEYS;
>
>
>
Thank you Patrick.
Admittedly, ENABLE KEYS is something new to me so I think I'll have
fun tackling this issue. I just solved a build problem in FreeBSD so
I'm going to start investigating this bug.
Cheers,
Toru
On Wed, Jun 2, 2010 at 6:20 AM, Patrick Crews <email address hidden> wrote: /bugs.launchpad .net/bugs/ 588487 10_key` varchar(10), 1024_key` varchar(1024), 10_key` ), 1024_key` ), hpubzfjxwqacdiw yekwemegyaluzyt nccflbvqnqnmfvv lhitckzgppyilih mleccmmxqxcilxq vfikqseftdkgtlq zbwpucapktdeqxn dcqytizhxaaiyas hfuwbyynvenjcsm asklnxxtbzrqxmo upppjcctptgoksl eizxkrbednzzwgv lnnghjvvtlpajya lhsygtjrhjxreyw ihgnxlevtsvfzsz tftgvgzkqhwpnbz tbcpoqdmhgjffok jvoae', 'from', -2114322432, 'mean', 't', -1076690944, NULL) , ('r', 'qxermmjkovqnoq hpubzfjxwqacdiw yekwemegyaluzyt nccflbvqnqnmfvv lhitckzgppyilih mleccmmxqxcilxq vfikqseftdkgtlq zbwpucapktdeqxn dcqytizhxaaiyas hfuwbyynvenjcsm asklnxxtbzrqxmo upppjcctptgoksl eizxkrbednzzwgv lnnghjvvtlpajya lhsygtjrhjxreyw ihgn', 0, 'his', 'eqxermmjkovqno qhpubzfjxwqacdi wyekwemegyaluzy tnccflbvqnqnmfv vlhitckzgppyili hmleccmmxqxcilx qvfikqseftdkgtl qzbwpucapktdeqx ndcqytizhxaaiya shfuwbyynvenjcs masklnxxtbzrqxm oupppjcctptgoks lei', NULL, NULL) ;
> ** Changed in: drizzle
> Assignee: (unassigned) => Toru Maesaka (tmaesaka)
>
> --
> Using 'ALTER TABLE <> ENABLE KEYS' on a BlitzDB table locks up the server
> https:/
> You received this bug notification because you are a bug assignee.
>
> Status in A Lightweight SQL Database for Cloud and Web: New
>
> Bug description:
> Issuing an ALTER TABLE <name> ENABLE KEYS against a BlitzDB table causes Drizzle to lock up.
>
> Background:
> This was discovered while attempting to test BlitzDB with the Random Query Generator and part of the gendata (table creation + population script) process involves disabling/enabling keys during the initial table load.
>
> Test case:
> You will see appropriate warnings for key size being too long on the 1024 column as well as warnings for the truncation of data for the varchar_10 columns.
>
> You will also see an appropriate warning when we attempt to DISABLE KEYS (not supported).
>
> However, when we hit the ENABLE KEYS query, things lock up every time.
> drizzle> ALTER TABLE `C` ENABLE KEYS;
> Query OK, 0 rows affected, 1 warning (0 sec)
> ^ It appears that the query is processed correctly, however any queries after this point will not be productive, nor will additional attempts to connect to the server.
>
>
> CREATE TABLE `C` (
> `col_varchar_
> `col_varchar_10` varchar(10),
> `col_int` int,
> `col_varchar_
> `col_varchar_1024` varchar(1024),
> `col_int_key` int,
> pk integer auto_increment,
> /*Indices*/
> key (`col_varchar_
> key (`col_varchar_
> key (`col_int_key` ),
> primary key (pk)) ENGINE=blitzdb ;
> ALTER TABLE `C` DISABLE KEYS ;
> INSERT /*! IGNORE */ INTO C VALUES ('xermmjkovqnoq
> COMMIT;
> ALTER TABLE `C` ENABLE KEYS;
>
>
>
--
Toru Maesaka <email address hidden>