Re: GEO Search with large table is very slow
Posted by:
Rick James
Date: March 13, 2009 07:53PM
As Markus suggests, individual indexes makes sense in this case. The reason is that it can't really make use of more than one field in an index anyway. Plus, one index may be better than another depending on the constants.
Please provide
* SHOW CREATE TABLE tbl\G -- need to see types and index(es)
* SHOW TABLE STATUS LIKE 'tbl'\G
* EXPLAIN SELECT ...\G -- especially after adding indexes and trying different constants
and surround them with [ code ] and [ / code ]
Subject
Views
Written By
Posted
9610
March 11, 2009 01:35PM
3496
March 11, 2009 07:36PM
3600
March 13, 2009 08:12AM
Re: GEO Search with large table is very slow
3309
March 13, 2009 07:53PM
3545
March 18, 2009 09:27AM
5545
March 18, 2009 09:02PM
3678
April 04, 2009 07:03AM
3697
April 04, 2009 12:51PM
3152
April 06, 2009 09:59AM
2986
April 06, 2009 07:38PM
3260
March 15, 2009 07:41PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.