mhansson/martin@linux-st28.site 1da8451d4d bug#28570: handler::index_read() is called with different find_flag when ...

ORDER BY is used

The range analysis module did not correctly signal to the 
handler that a range represents a ref (EQ_RANGE flag). This causes 
non-range queries like 
SELECT ... FROM ... WHERE keypart_1=const, ..., keypart_n=const 
ORDER BY ... FOR UPDATE
to wait for a lock unneccesarily if another running transaction uses
SELECT ... FOR UPDATE on the same table.

Fixed by setting EQ_RANGE for all range accesses that represent 
an equality predicate.

2007-08-15 09:23:44 +02:00

77 KiB

Raw Blame History

View Raw