After what action are you indexes becoming invalid? Are you running nightly
maintenance? What is the table type?
-----Original Message-----
From: Jude Insley
To: [EMAIL PROTECTED]
Sent: 5/21/04 6:00 AM
Subject: Index cardinality lost
We have a set of tables which are losing the cardinality on the first
part
of the primary key. A simple CHECK TABLE or ANALYZE table restores the
cardinality. We are running MySQL 4.0.18 on Solaris 8.
*************************** 1. row ***************************
Table: UserSessions
Non_unique: 0
Key_name: PRIMARY
Seq_in_index: 1
Column_name: sessionID
Collation: A
Cardinality: NULL
Sub_part: NULL
Packed: NULL
Null:
Index_type: BTREE
Comment:
*************************** 2. row ***************************
Table: UserSessions
Non_unique: 0
Key_name: PRIMARY
Seq_in_index: 2
Column_name: userID
Collation: A
Cardinality: 164142
Sub_part: NULL
Packed: NULL
Null:
Index_type: BTREE
Comment:
Is this a bug? Additional information - these tables are replicated
between two similar servers (Solaris 8, MySQL 4.0.18) and are populated
exclusively using INSERT DELAYED SQL statements.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
