[MDEV-8366] Query cache invalidation and lock tables with write lock Created: 2015-06-23  Updated: 2015-06-24  Resolved: 2015-06-24

Status: Closed
Project: MariaDB Server
Component/s: Query Cache
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: roberto spadim Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

Hi guys, i think we have a problem with lock tables write lock and query cache
when we execute a LOCK TABLE xxx WRITE, shouldn't the query cache for that table be avoid? cause i can execute select with that table and get results even i have lock table with write lock

in other words, what i'm thinking about:
1) lock table with write should invalidate query cache table
2) locked tables should be checked before returning query cache data to client (for example, if we got the query from cache, check if we have a locked table with LOCK TABLE command, if yes, don't fetch from query cache)

this happen with any engine (including innodb but not common)



 Comments   
Comment by Elena Stepanova [ 2015-06-24 ]

Hi Roberto,

That's what query_cache_wlock_invalidate option is for, is it not?

Generated at Thu Feb 08 07:26:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.