Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
Description
In MySQL, Optimizer trace is a JSON object recording the execution path through the optimizer, decisions that were made and the reasons for them. See https://dev.mysql.com/doc/internals/en/optimizer-tracing.html
Users were asking for MariaDB to have a similar feature.
Attachments
Issue Links
- blocks
-
MDEV-7239 explain index choice
-
- Closed
-
- includes
-
MDEV-17929 Optimizer trace support for different parts of the server
-
- Closed
-
-
MDEV-17930 Optimizer trace: what's on the execution path when trace=off?
-
- Closed
-
-
MDEV-18117 Crash with Explain extended when using limit rows examined
-
- Closed
-
-
MDEV-18172 Benchmarking 10.4 for optimizer trace
-
- Closed
-
-
MDEV-18306 Optimizer_trace has invalid JSON near rows_estimation
-
- Closed
-
-
MDEV-18489 Limit the memory used by the optimizer trace
-
- Closed
-
- relates to
-
MDEV-12980 Index hints for loose scan
-
- Confirmed
-
-
MDEV-18670 Document optimizer trace
-
- Closed
-
-
MDEV-20440 Optimizer trace: print more details about semi-join optimization
-
- Closed
-
-
MDEV-18527 Optimizer trace for DELETE query shows table:null
-
- Closed
-
-
MDEV-18528 Optimizer trace support for multi-table UPDATE and DELETE
-
- Closed
-
-
MDEV-18741 Optimizer trace: multi-part key ranges are printed incorrectly.
-
- Closed
-
-
MDEV-18822 investigate performance regressions in 10.4
-
- Stalled
-
-
MDEV-19160 JSON_DETAILED output unnecessarily verbose (Part Time project)
-
- Closed
-
-
MDEV-20444 More information regarding access of a table to be printed inside the optimizer_trace
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Priority | Major [ 3 ] | Critical [ 2 ] |
Labels | optimizer |
Fix Version/s | 10.2.0 [ 14601 ] | |
Fix Version/s | 10.1.0 [ 12200 ] |
Workflow | defaullt [ 38927 ] | MariaDB v2 [ 42476 ] |
Workflow | MariaDB v2 [ 42476 ] | MariaDB v3 [ 61431 ] |
Fix Version/s | 10.2 [ 14601 ] |
Link | This issue relates to MDEV-12980 [ MDEV-12980 ] |
Comment |
[ Alas, optimizer w/TokuDB seems to be tremendously broken after 10.1.23.
The only recommendation I've got is to create a ticket on Percona for that, still not done though. Stay on 10.1.23 for now if you want it stable. ] |
Link | This issue is part of MDEV-14666 [ MDEV-14666 ] |
Link | This issue is part of PT-67 [ PT-67 ] |
Labels | optimizer | gsoc18 optimizer |
Assignee | Sergei Petrunia [ psergey ] |
Description | port optimizer trace from 5.6 |
In MySQL, Optimizer trace is a JSON object recording the execution path through the optimizer, decisions that were made and the reasons for them. See https://dev.mysql.com/doc/internals/en/optimizer-tracing.html
Users were asking for MariaDB to have a similar feature. |
Assignee | Sergei Petrunia [ psergey ] | Varun Gupta [ varun ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Attachment | screenshot-1.png [ 46685 ] |
Attachment | mdev6111-example-trace-from-mysql8.txt [ 46686 ] |
Epic Link | PT-76 [ 68557 ] |
Team | Server DEV |
Link |
This issue includes |
Link |
This issue includes |
Fix Version/s | 10.4 [ 22408 ] |
Link |
This issue includes |
Assignee | Varun Gupta [ varun ] | Sergei Petrunia [ psergey ] |
Status | In Progress [ 3 ] | In Review [ 10002 ] |
Link |
This issue includes |
Link |
This issue includes |
Link |
This issue includes |
Link |
This issue relates to |
Link |
This issue relates to |
Assignee | Sergei Petrunia [ psergey ] | Varun Gupta [ varun ] |
Status | In Review [ 10002 ] | Stalled [ 10000 ] |
Component/s | Optimizer [ 10200 ] | |
Fix Version/s | 10.4.3 [ 23230 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Link |
This issue relates to |
Link |
This issue relates to |
Link |
This issue relates to |
Link | This issue relates to MDEV-18822 [ MDEV-18822 ] |
Link |
This issue relates to |
Link |
This issue relates to |
Link | This issue relates to MENT-455 [ MENT-455 ] |
Workflow | MariaDB v3 [ 61431 ] | MariaDB v4 [ 132320 ] |