Bug #8893 Using "SELECT MAX(ID)" with Multiple-Column Indexes
| Submitted: | 2 Mar 2005 14:51 | Modified: | 9 Mar 2005 3:41 |
|---|---|---|---|
| Reporter: | Ralph Runge | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S2 (Serious) |
| Version: | 4.1.10 | OS: | Any (all) |
| Assigned to: | Igor Babaev | CPU Architecture: | Any |
[2 Mar 2005 14:51]
Ralph Runge
[2 Mar 2005 22:05]
Jorge del Conde
Verified w/latest bk changeset in 4.1
[5 Mar 2005 4:22]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/22684
[5 Mar 2005 22:21]
Igor Babaev
The first releases with this fix will be: 4.1.11 and 5.0.3.
ChangeSet
1.2083 05/03/04 20:24:13 igor@linux.local +4 -0
logging_ok:
Logging to logging@openlogging.org accepted
func_group.result, func_group.test:
Added a test case for bug #8893.
opt_sum.cc:
A misplaced initialization for the returned parameter
prefix_len in the function find_key_for_maxmin caused
usage of a wrong key prefix by the min/max optimization
in cases when the matching index was not the first index
that contained the min/max field.
[9 Mar 2005 3:41]
Paul DuBois
Noted in 4.1.11, 5.0.3 changelogs.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
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.