Bug #41042 binlog-format system variable missing
Submitted: 26 Nov 2008 6:15 Modified: 26 Dec 2008 7:35
Reporter: Mark Palmer Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Options Severity:S3 (Non-critical)
Version:5.1.29 OS:Linux (Red Hat 4 32 bit)
Assigned to: CPU Architecture:Any
Tags: binlog-format

[26 Nov 2008 6:15] Mark Palmer
Description:
Installed 5.1.29 on new OS install using binaries.  Attempt to set binlog-format=row in my.cnf and server won't start.  Attempt to set in mysql monitor and get error for unknown variable.  Do a show variables and variable is not listed.  Also noted that 184 variables were listed and I recall in 5.1.23 there are over 200.  

How to repeat:
Install 5.1.29 binaries on Red Hat 4.  Using mysql monitor do show variables or show variables like '%bin%' and binlog_format not listed.

Suggested fix:
Should work as documented
[26 Nov 2008 7:35] Valeriy Kravchuk
Looks like this is fixed in 5.1.30 that should be released soon officially:

C:\Program Files\MySQL\MySQL Server 5.0\bin>mysql -uroot -proot -P3310 test
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 5
Server version: 5.1.30-community MySQL Community Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show variables like '%binlog%';
+--------------------------------+------------+
| Variable_name                  | Value      |
+--------------------------------+------------+
| binlog_cache_size              | 32768      |
| binlog_format                  | STATEMENT  |
| innodb_locks_unsafe_for_binlog | OFF        |
| max_binlog_cache_size          | 4294967295 |
| max_binlog_size                | 1073741824 |
| sync_binlog                    | 0          |
+--------------------------------+------------+
6 rows in set (0.00 sec)
[27 Dec 2008 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".