Hi,
It's InnoDB on 5.0.51. The only thing I can think of that *may* be
different about this is that this index used to be on a composite key
(some_id, some_varchar) but then the VARCHAR column got dropped. Other
than that, it's just a plain index on an INT(11).
Morten
On Jun 16, 2009, at 5:51 AM, Andrew Braithwaite wrote:
> Hi,
>
> Is your table MyISAM or InnoDB?
>
> Andrew
>
> -----Original Message-----
> From: Morten [mailto:my.lists@stripped]
> Sent: 15 June 2009 21:23
> To: mysql@stripped
> Subject: The size of an index (INDEX_LENGTH)
>
>
> Hi,
>
> I dropped an index on a table with 25M records today. The INDEX_LENGTH
> in information_schema.tables shrank from 3834642432 to 3215982592, ie.
> ~618Mb difference
>
> The index was on an int(11) column.
>
> That means each index key takes up ~618Mb/25M ~= 25 bytes but that
> doesn't sound right? Is that true, or is information_schema.tables
> unreliable or?
>
> Thanks,
>
> Morten
>
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=1
>
