Bug #58010 The scope of max_allowed_packet is set to Global
Submitted: 5 Nov 2010 10:55 Modified: 5 Nov 2010 11:26
Reporter: Daogang Qu Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.1+ OS:Any
Assigned to: CPU Architecture:Any

[5 Nov 2010 10:55] Daogang Qu
Description:
The scope of max_allowed_packet is set to Global.
But it has both scopes (global and session).

http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_max_allowed_pac...

How to repeat:

Read the following doc:
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_max_allowed_pac...

Suggested fix:
Please update the doc.
[5 Nov 2010 11:26] Jon Stephens
According to the page cited:

"As of MySQL 5.1.31, the session value of this variable is read only. Before 5.1.31, setting the session value is permitted but has no effect."

For all practical purposes this has always been a global variable only, which is at it should be, and the changes in 5.1.31 were simply to clarify that this was the intended behaviour. (Think about this -- do you really want *any* user to be able to change this value?)

More info in BUG#22891 and BUG#32223.