Skip to content
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

Wrong COM_STMT_PREPARE response size for versions above v1.3.5 #1062

Closed
oytuntez opened this issue Jun 20, 2017 · 4 comments
Closed

Wrong COM_STMT_PREPARE response size for versions above v1.3.5 #1062

oytuntez opened this issue Jun 20, 2017 · 4 comments
Assignees
Milestone

Comments

@oytuntez
Copy link

This is a sample error we receive when we upgraded to 1.3.6 or 1.3.7:

Wrong COM_STMT_PREPARE response size. Received 7 (SQL: select * from userswhereid = 3707 limit 1)

I am not sure what this is about, can you enlighten me? Literally no errors in the log file. I see this warning only:

2017-06-20 15:37:30 ProxySQL_Admin.cpp:2921:flush_mysql_variables___database_to_runtime(): [WARNING] Impossible to set not existing variable ping_interval_server with value "120000". Deleting. If the variable name is correct, this version doesn't support it

@renecannao
Copy link
Contributor

is maybe this a duplicate of #965 ?

@Ninpo
Copy link

Ninpo commented Jun 22, 2017

I've got the same problem with Laravel and PDO trying to prepare "set session sql_mode=''".

PHP 5.5 with Debian Trusty. Problem doesn't exist in 1.3.5 but does exist in 1.3.6, 1.3.7 and the 1.4.1 branch on github. PHP using mysqlnd.

@renecannao
Copy link
Contributor

This issue was indeed introduced in 1.3.6 as it is tracking sql_log_bin, sql_mode and time_zone .
As @Ninpo pointed, this is is due to Laravel and PDO trying to prepare set session sql_mode.
Using prepared statements for set sql_mode is very inefficient (Lavarel shouldn't so that!), but ProxySQL should handle it, therefore I call it a bug in ProxySQL.
Working on this bug now.

renecannao added a commit that referenced this issue Jul 17, 2017
Forward to backend SET commands with prepared statements
@renecannao renecannao self-assigned this Jul 19, 2017
@renecannao renecannao added this to the 1.3.9 milestone Jul 19, 2017
renecannao added a commit that referenced this issue Jul 19, 2017
Forward to backend SET commands with prepared statements
@renecannao
Copy link
Contributor

Fixed in 1.3.9 and 1.4.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants