Bug #31839 5.0 Variable Inaccuracies

• Submitted: 25 Oct 2007 9:51
• Modified: 25 Oct 2007 13:00
• Reporter: Trent Lloyd
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 5.0
• OS: Any
• Assigned to: Peter Lavin
• CPU Architecture: Any

[25 Oct 2007 9:51] Trent Lloyd

Description:
The following pages:
http://dev.mysql.com/doc/refman/5.0/en/mysqld-option-tables.html
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html

Have some inaccuracies, as I understand it they are generated from the same source.

* binlog_cache_size *
Claims to be both GLOBAL and SESSION scope, but actually only has GLOBAL scope.

* innodb_buffer_pool_size *
Claims to be both GLOBAL and SESSION scope, but actually only has GLOBAL scope (is not dynamic at all, so SESSION scope makes no sense)

* innodb_max_dirty_pages_pct *
Claims to be both GLOBAL and SESSION scope, but actually only has GLOBAL scope.

* query_cache_limit *
Claims to be both GLOBAL and SESSION scope, but actually only has GLOBAL scope.

* query_cache_size *
Claims to be both GLOBAL and SESSION scope, but actually only has GLOBAL scope.

* table_cache *
Claims to be both GLOBAL and SESSION scope, but actually only has GLOBAL scope.

* thread_cache_size *
Claims to be both GLOBAL and SESSION scope, but actually only has GLOBAL scope.

How to repeat:
N/A

Suggested fix:
N/A

[25 Oct 2007 9:56] Trent Lloyd

I left one out;

* innodb_log_buffer_size *

The same as innodb_buffer_pool_size;
Claims to be both GLOBAL and SESSION scope, but actually only has GLOBAL scope (is not
dynamic at all, so SESSION scope makes no sense)

[25 Oct 2007 13:00] Peter Lavin

Changed scope for table_cache_size and table_cache_limit, others already
changed. Thanks Trent.