[MDEV-4676] QUERY CACHE - partition lock prune and invalidation query cache Created: 2013-06-18 Updated: 2014-09-22 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Query Cache |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | roberto spadim | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | querycache, querycache_insert | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Description |
|
after we will have partition lock prune, this is nice, but query cache need information about partition being used in update/delete to invalidade only queries that use the table + partition, not only the table i send a bug report to mysql at: http://bugs.mysql.com/bug.php?id=69501 since we can have more than 8000 partitions, could be nice a query cache map in partition information, like
1 = an id to group partitions With this we could better remove queries from query cache when one partition or a group of partitions (with same QUERY_CACHE_ID) change, or dont cache some partitions (QUERY_CACHE_ID=SQL_NO_CACHE) This change qc_info.cc plugin since we have a QUERY_CACHE_TABLE that have all tables used, we should add the PARTITION_QC_ID column to allow a better understand of what partition was used, (maybe set to NULL when table don't have partition) |