On Mon, Mar 17, 2008 at 11:35 PM, Sebastian Mendel <[EMAIL PROTECTED]> wrote: > hu? ... i am pretty sure i had a similar problem, i solved this by adding > the column with the order to the index, which 'solved' the filesort (except > the ORDER is in reverse) I don't think we can lose the filesort will the current criteria, but I am by no means an expert. I would be quite interested in any techniques to further optimize the query.
> but it requires more resources, or? 1. The index will use more disk space (not that it probably matters much). 2. Inserts and updates will take longer (might be important, might not). 3. I have had queries take a performance hit from adding columns to composite index's. Most of my work I have done on 3.23 and I am sure mysql has gotten smarter since then, but old habits are hard to lose. -- Rob Wultsch -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
