MySQL Bugs: #56988: sql_bin_log is not reported in SHOW SESSION VARIABLES;

Bug #56988	sql_bin_log is not reported in SHOW SESSION VARIABLES;
Submitted:	23 Sep 2010 22:25	Modified:	24 Sep 2010 4:58
Reporter:	Daniel Lo	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Options	Severity:	S4 (Feature request)
Version:	5.0.89+?	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	show variables, sql_bin_log

Description:
sql_bin_log is a variable available to turn off binary logging for the session.

However, when I do

mysql> show session variables like 'sql_log_bin';
Empty set (0.00 sec)

The variable does not appear.

sql-log-bin documentation
http://dev.mysql.com/doc/refman/5.0/en/set-sql-log-bin.html

How to repeat:
show session variables like 'sql_log_bin';

Verified on 5.0.92. Note that this is already fixed in 5.1:

macbook-pro:5.1 openxs$ bin/mysql -uroot test
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.1.52-debug Source distribution

Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL v2 license

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show session variables like '%sql%';
+--------------------------+----------------------+
| Variable_name            | Value                |
+--------------------------+----------------------+
| sql_auto_is_null         | ON                   |
| sql_big_selects          | ON                   |
| sql_big_tables           | OFF                  |
| sql_buffer_result        | OFF                  |
| sql_log_bin              | ON                   |
| sql_log_off              | OFF                  |
| sql_log_update           | ON                   |
| sql_low_priority_updates | OFF                  |
| sql_max_join_size        | 18446744073709551615 |
| sql_mode                 |                      |
| sql_notes                | ON                   |
| sql_quote_show_create    | ON                   |
| sql_safe_updates         | OFF                  |
| sql_select_limit         | 18446744073709551615 |
| sql_slave_skip_counter   |                      |
| sql_warnings             | OFF                  |
+--------------------------+----------------------+
16 rows in set (0.00 sec)

and, taking into account current status of 5.0 (end of lifecycle), I doubt this feature will be implemented in 5.0.