Re: Why would a SELECT COUNT(*)... WHERE... take way way longer than SELECT COUNT(primary_key)... WHERE... ?

2006-06-19 Thread cvizitiu
Alex Arul wrote: count(*) is slow in innodb due to Multi Versioning. Which table type are you using ? Hi Alex, Thanks for answering; All tables are MyISAMs. I'm beginning to wonder if I am not taxed heavily for using floats for the geographic coordinates. -- MySQL General Mailing List

Re: Why would a SELECT COUNT(*)... WHERE... take way way longer than SELECT COUNT(primary_key)... WHERE... ?

2006-06-17 Thread Alex Arul
count(*) is slow in innodb due to Multi Versioning. Which table type are you using ? Thanx Alex On 6/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi everybody, MySQL 5.0.21 running on RedHat EL4, 2GHz CPU, 2,5GB RAM, RAID5/128MB RAM. At one point I had to issue the following query on a

Re: Why would a SELECT COUNT(*)... WHERE... take way way longer than SELECT COUNT(primary_key)... WHERE... ?

2006-06-17 Thread Jad madi
Innodb tables do not cache the rowcount like MyISAM tables do, so mysql has to walk the entire table to get a count. If you have a unique index, it should be able to scan that instead, which will be faster. On Sat, 2006-06-17 at 20:32 +0530, Alex Arul wrote: count(*) is slow in innodb due to

Why would a SELECT COUNT(*)... WHERE... take way way longer than SELECT COUNT(primary_key)... WHERE... ?

2006-06-09 Thread cvizitiu
Hi everybody, MySQL 5.0.21 running on RedHat EL4, 2GHz CPU, 2,5GB RAM, RAID5/128MB RAM. At one point I had to issue the following query on a 1.8GB 42mil records table: SELECT COUNT(*) FROM geoRecord WHERE geoRecord.geolatitude IS NOT NULL ; As it took forever to complete (I mean more than