-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySQL Query Cache Invalidation with comment_propagation #3561
Comments
Thanks @zmariscal , I will have a look! |
From MySQL Bug #40986:
This is possibly a workaround. |
Any update on this issue? Anything I can do to help? |
This is the current implementation. I am forwarding this to our DBM team. |
Hi @zmariscal, which version of MySQL are you querying and is it self-hosted, Aurora, etc? |
The AWS Engine version is as follows: 5.7.mysql_aurora.2.11.2 |
Ok, thanks for the report. We've opened a ticket and will get back to you when we know more |
Current Behaviour:
When enabling
comment_propagation
for the mysql2 adapter, we noticed that it invalidates MySQL's query cache. It appears to be potentially linked to a known MySQL issue documented here: MySQL Bug #40986. The specific line in the codebase possibly implicated in this behavior can be found here.Expected Behaviour:
At the very least, there should be documentation outlining the implications of enabling
comment_propagation
.Steps to Reproduce:
Environment:
The text was updated successfully, but these errors were encountered: