Bug #108750 TABLE ACCESS SERVICE INDEX READ MAP ISSUES

• Submitted: 12 Oct 2022 10:08
• Modified: 14 Oct 2022 15:56
• Reporter: Marc ALFF
• Status: Closed
• Category: MySQL Server: Performance Schema
• Severity: S3 (Non-critical)
• Version: 8.0.26
• OS: Any
• Assigned to: Marc ALFF
• CPU Architecture: Any

[12 Oct 2022 10:08] Marc ALFF

Description:
In the TABLE ACCESS SERVICE,

when using an index to perform a read_map / index_nest_same loop:

1)

read_map calls handler::ha_index_read_idx_map()

This opens and closes an index silently,
closing the current index as a side effect

Fix: Use handler::ha_index_read_map() instead

2)

next_same calls handler::ha_index_next_same()
with a key_length of 0.

This affects storage engines implementation that actually make use
of the key and key length.

Fix: Populate the key length.

---

Entered in category performance schema,
there are no categories for server components.

How to repeat:
Execute under a debugger and inspect state.

Suggested fix:
Per description

[14 Oct 2022 15:56] Jon Stephens

Fixed in MySQL 8.0.32.

Closed.