More interesting rezults, after runnig some check/repair/analyze commands
in sequence on the same table:

mysql> repair table http_refer extended;
+-----------------+--------+----------+----------+
| Table           | Op     | Msg_type | Msg_text |
+-----------------+--------+----------+----------+
| test.http_refer | repair | status   | OK       |
+-----------------+--------+----------+----------+
1 row in set (0.50 sec)

mysql> check table http_refer extended;
+-----------------+-------+----------+------------------------------------+
| Table           | Op    | Msg_type | Msg_text                           |
+-----------------+-------+----------+------------------------------------+
| http_refer      | check | error    | Key in wrong position at page 8192 |
| test.http_refer | check | error    | Corrupt                            |
+-----------------+-------+----------+------------------------------------+
2 rows in set (0.00 sec)

mysql> check table http_refer extended;
+-----------------+-------+----------+------------------------------------+
| Table           | Op    | Msg_type | Msg_text                           |
+-----------------+-------+----------+------------------------------------+
| http_refer      | check | warning  | Table is marked as crashed         | 
<-New Line
| http_refer      | check | error    | Key in wrong position at page 8192 |
| test.http_refer | check | error    | Corrupt                            |
+-----------------+-------+----------+------------------------------------+
3 rows in set (0.00 sec)

mysql> analyze table http_refer ;
+-----------------+---------+----------+-------------------------------------------------+
| Table           | Op      | Msg_type | 
Msg_text                                        |
+-----------------+---------+----------+-------------------------------------------------+
| test.http_refer | analyze | error    | Can't open file: 'http_refer.MYD'. 
(errno: 145) |
+-----------------+---------+----------+-------------------------------------------------+
1 row in set (0.00 sec)

mysql> repair table http_refer extended;
+-----------------+--------+----------+----------+
| Table           | Op     | Msg_type | Msg_text |
+-----------------+--------+----------+----------+
| test.http_refer | repair | status   | OK       |
+-----------------+--------+----------+----------+
1 row in set (0.34 sec)

mysql> analyze table http_refer ;
+-----------------+---------+----------+------------------------------------+
| Table           | Op      | Msg_type | Msg_text                           |
+-----------------+---------+----------+------------------------------------+
| http_refer      | analyze | error    | Key in wrong position at page 8192 |
| test.http_refer | analyze | error    | Corrupt                            |
+-----------------+---------+----------+------------------------------------+
2 rows in set (0.01 sec)

mysql> check table http_refer extended;
+-----------------+-------+----------+------------------------------------+
| Table           | Op    | Msg_type | Msg_text                           |
+-----------------+-------+----------+------------------------------------+
| http_refer      | check | warning  | Table is marked as crashed         |
| http_refer      | check | error    | Key in wrong position at page 8192 |
| test.http_refer | check | error    | Corrupt                            |
+-----------------+-------+----------+------------------------------------+
3 rows in set (0.00 sec)

What does it mean?


At 10:25 AM 3/19/01 Monday +0200, you wrote:
>Hi,
>         I'm a bit desperate and have some questions to ask.
>
>I'm working with my own compiled server 3.23.33 on SuSe 7.0
>I have table:
>
>mysql> desc test.http_refer;
>+-------+------------------+------+-----+---------+----------------+
>| Field | Type             | Null | Key | Default | Extra          |
>+-------+------------------+------+-----+---------+----------------+
>| rid   | int(10) unsigned |      | PRI | NULL    | auto_increment |
>| refer | varchar(255)     | YES  | UNI | NULL    |                |
>+-------+------------------+------+-----+---------+----------------+
>2 rows in set (0.00 sec)
>
>The data of table is referrer field from our Apache server logs. Most of
>it is some URLs from search engines, for example:
>
>http://listings.altavista.com/scripts/gt.dll?type=main&method=search&kl=lt&dd=nsp&stq=30&rank=30&q=sajungos&nbq=10&glastQuery=Keywords%3dsajungos&grank=0
> 
>
>
>Some rows have refer of 255 chars long.
>
>Why queries:
>
>select rid,length(refer) from http_refer
>select rid,max(length(refer)) from http_refer group by refer
>
>WORKS just fine, while queries:
>
>select length(refer) from http_refer;
>select max(length(refer)) from http_refer;
>select max(length(refer)) from http_refer group by refer;
>
>just HANGS, and I have kill them after a while???
>
>Is it incorrect queries or problems with table data or maybe these queries 
>is long runnig?
>
>If anyone could shed some light on this issue I would be very appreciate.
>Thanks anyway.


Saulius Gurklys
mailto:[EMAIL PROTECTED]


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to