Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL++ - Programming with the C++ API to MySQL
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
ODBC - ODBC with the MySQL Connector/ODBC driver
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
mysql:it 's a db not a dbms how it 's possible?!
Does the binary log enabling affect the MySQL performances?
Strange behavior, Table Level Permission
FULLTEXT query format question
Preventing Duplicate Entries
Comparing and writing out BLOBS
Executing MySQL Commands From Within C Program
Can 't access mysql after kernel upgrade
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Downgrade Mysql from 4 to 3 23
MySQL Cluster Software
mysql test 4 1 fails with the gis test
ERROR 2002: Can 't connect to local MySQL server through socket
Getting Identity after INSERT
Update one field with more fields from another table
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
mysql have same function mthod as Oracle decode()
 
number of rows in EXPLAIN for unpacked vs packed tables

number of rows in EXPLAIN for unpacked vs packed tables

2006-06-30       - By Dan Buettner

 Back
Reply:     1     2     3  

Cor -

Those numbers are an estimate, not a hard number, of how many rows
MySQL thinks it will have to exmaine to find what you're looking for.

They could be different because your compressed table is brand-new and
all the indexes are clean and up to date, whereas your original table
has possibly been inserted, updated, and deleted from, causing the key
information to be less accurate.

You could try running a CHECK TABLE <tablename> EXTENDED on the old
one, which should update all the key info, and then checking your
EXPLAIN results again.  Be aware it could take a while for a large
table and will lock the table for the duration.

If your indexes are different on the compressed table that would make
a difference too, as MySQL might well be basing its estimate off a
different index.

Dan



On 6/30/06, C.R.Vegelin <cr.vegelin@(protected)> wrote:
> Hi All,
>
> I compressed a MyISAM table successfully with MYISAMPACK, followed by
MYISAMCHK.
> Both tables (MyISAM + Compressed ) have exactly the same number of rows with
Count(*).
> But when I give a SELECT query with EXPLAIN on both tables, I get different
number of rows.
> For example: EXPLAIN SELECT ... FROM data ... shows 1983 rows,
> but the same EXPLAIN SELECT ... FROM pack ... shows 2064 rows.
> Any idea why ?
>
> Regards, Cor
>

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=mysql@(protected)