Pete Harlan wrote:
> FYI,
>
> 4.1.16 appears not to be using prefixes of compound indexes when doing
> updates. Reverting to 4.1.15, or adding an index consisting of only
> the desired field, restores reasonable behavior.
>
> I have added feedback to a possibly-related bug,
> <http://bugs.mysql.com/bug.php?id=15935>, but wanted to send a message
> on the list in case someone is having trouble with 4.1.16 and doesn't
> know why, or is thinking of upgrading and might want to wait, or knows
> a solution to this problem besides downgrading.
i noticed an increased load average on our servers, then i switched
back to 4.1.15.
now i'm waiting for 4.1.17 :)
chris
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
