Release lock on table statistics after query plan created | Stop ANALYZE TABLE from flushing table definition cache
Bug #1704195 reported by
Sveta Smirnova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Won't Fix
|
Wishlist
|
Unassigned | |||
5.6 |
Fix Released
|
Wishlist
|
Laurynas Biveinis | |||
5.7 |
Fix Released
|
Wishlist
|
Laurynas Biveinis |
Bug Description
Description:
Under concurrent environment running ANALYZE TABLE could lead to situation when hundreds of tables are in state "Waiting for table flush".
How to repeat:
Read https:/
Suggested fix:
Implement new type of lock which holds statistics only and release it immediately after Optimizer creates execution plan.
tags: | added: performance |
summary: |
- Release lock on table statistics after query plan created + Release lock on table statistics after query plan created | stop ANALYZE + TABLE from flushing table definition cache |
summary: |
- Release lock on table statistics after query plan created | stop ANALYZE + Release lock on table statistics after query plan created | Stop ANALYZE TABLE from flushing table definition cache |
To post a comment you must log in.
Experimental 5.6 fix (applies only to non-partitioned InnoDB tables) at https:/ /github. com/laurynas- biveinis/ percona- server/ tree/bug1704195 -5.6-trunk