Bug #57938 mismatch between doc and server behaviour wrt scope of some system variables
Submitted: 2 Nov 2010 20:36 Modified: 5 Nov 2010 14:46
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.1, 5.5 OS:Any
Assigned to: Paul DuBois CPU Architecture:Any

[2 Nov 2010 20:36] Guilhem Bichot
Description:
About 5.1:
http://dev.mysql.com/doc/refman/5.1/en/mysqld-option-tables.html
says that
sql_big_selects is session and global ("Both"); but testing shows that
  SET GLOBAL sql_big_selects=1;
fails ("variable 'sql_big_selects' is a SESSION variable and can't be used with SET GLOBAL"). So it's actually session-only.

About 5.5:
http://dev.mysql.com/doc/refman/5.5/en/mysqld-option-tables.html
says that
sql_buffer_result is session-only, but SET GLOBAL works for it.

How to repeat:
see description.

Suggested fix:
fix the manual
[2 Nov 2010 20:51] MySQL Verification Team
Thank you for the bug report.

mysql 5.1> SET GLOBAL sql_big_selects=1;
ERROR 1228 (HY000): Variable 'sql_big_selects' is a SESSION variable and can't be used with SET GLOBAL
mysql 5.1
[5 Nov 2010 14:46] Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.