Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.37, 10.0.11
-
None
Description
init_read_record() performs condition pushdown, but doesn't honor HA_MUST_USE_TABLE_CONDITION_PUSHDOWN flag.
Reported by Kentoku Shiba. More details to be added.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | HA_MUST_USE_TABLE_CONDITION_PUSHDOWN is not accounted in | HA_MUST_USE_TABLE_CONDITION_PUSHDOWN is not accounted by init_read_record() |
| Labels | spider |
| Fix Version/s | 10.0.13 [ 16000 ] |
| Workflow | defaullt [ 42209 ] | MariaDB v2 [ 44445 ] |
| Labels | spider | plugins spider |
| Assignee | Sergei Golubchik [ serg ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Fix Version/s | 10.0.13 [ 16300 ] | |
| Fix Version/s | 10.0 [ 16000 ] |
| Affects Version/s | 10.1.0 [ 12200 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | MariaDB v2 [ 44445 ] | MariaDB v3 [ 63794 ] |
| Workflow | MariaDB v3 [ 63794 ] | MariaDB v4 [ 147938 ] |
I'd prefer to drop HA_MUST_USE_TABLE_CONDITION_PUSHDOWN flag completely. If the user wants to have condition pushdown — she should enable it. In fact, it should be enabled by default. And only disabled as a temporary workaround for some misbehaving engine (that we don't have, at the moment at all).