Bug #69501 partition lock / partition query cache

• Submitted: 18 Jun 2013 15:26
• Modified: 7 Jul 2017 9:08
• Reporter: Roberto Spadim (Basic Quality Contributor)
• Status: Won't fix
• Category: MySQL Server: Query Cache
• Severity: S5 (Performance)
• Version: 5.7.1
• OS: Any
• CPU Architecture: Any
• Tags: query cache partition

[18 Jun 2013 15:26] Roberto Spadim

Description:
hi guys, i was reading the partition lock prune, well since now we know what partition is being used, could we send this partition information to query cache?
example...
select SQL_CACHE * from table1 partition (p1)
update table1 partition (p2) set a=2

the second query shouldn't invalidade the first query cached query
today query cache have only table information, could we add partition information and avoid some query cache prunes?

How to repeat:
insert to some partitioned table
select with sql_cache in one partition
update other partition different from the first one
check if query is cached

Suggested fix:
add partition information inside query cache
needs changes to sql_cache.h sql_cache.cc and others handlers changes

[18 Jun 2013 17:07] MySQL Verification Team

https://mariadb.atlassian.net/browse/MDEV-4676

[25 Jul 2014 20:07] Sveta Smirnova

Thank you for the reasonable feature request.

[7 Jul 2017 9:08] Erlend Dahl

MySQL will no longer invest in the query cache, see:

http://mysqlserverteam.com/mysql-8-0-retiring-support-for-the-query-cache/