Bug #86405 | Stored procedure execution affected by query select in information_schema.tables | ||
---|---|---|---|
Submitted: | 22 May 2017 13:09 | Modified: | 31 May 2017 14:09 |
Reporter: | Atanaska Zoubeva | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.6.36-1 | OS: | Red Hat (el7, x64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | PROCEDURE, query_cache_type |
[22 May 2017 13:09]
Atanaska Zoubeva
[22 May 2017 13:11]
Atanaska Zoubeva
DB dump, stored procedure execution script, version information, my.cnf
Attachment: Report.tar.gz (application/gzip, text), 26.58 KiB.
[23 May 2017 6:11]
Atanaska Zoubeva
pcap trace of a broken session
Attachment: test.pcap (application/vnd.tcpdump.pcap, text), 139.50 KiB.
[23 May 2017 6:14]
Atanaska Zoubeva
Attached a pcap trace. Up until package 32 inclusive the requests are served without issues. Package 36 contains the select in the information schema which brakes the stored procedure and in package 58 the error code 1054 is returned with message "Unknown column 'testS' in 'field list'". Actually "testS" is the database name with capital S at the end and it is not used anywhere in the stored procedure.
[31 May 2017 14:09]
MySQL Verification Team
Hi, I can reproduce this problem but I doubt this will be fixed since we are retiring support for query cache. You can read more here: http://mysqlserverteam.com/mysql-8-0-retiring-support-for-the-query-cache/ all best Bogdan