[MDEV-14599] log_bin variable value is not evaluated as expexted Created: 2017-12-06  Updated: 2017-12-17  Resolved: 2017-12-17

Status: Closed
Project: MariaDB Server
Component/s: Admin statements
Affects Version/s: 5.5, 10.0, 10.1, 10.2.10, 10.2
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Oli Sennhauser Assignee: Sergei Golubchik
Resolution: Not a Bug Votes: 0
Labels: binary, log_bin, logs, upstream
Environment:

linux ubuntu 16.04


 Description   

[mysqld]
server_id = 42
log_bin = servername.dmz.corp.de_binlog

show master status;

+-------------------+----------+--------------+------------------+
 
| File              | Position | Binlog_Do_DB | Binlog_Ignore_DB |
 
+-------------------+----------+--------------+------------------+
 
| servername.000002 |      373 |              |                  |
 
+-------------------+----------+--------------+------------------+



 Comments   
Comment by Alice Sherepa [ 2017-12-06 ]

log_bin = servername.dmz.corp.de_binlog

10.2.10-MariaDB-log:

MariaDB [(none)]> show master status;
 
+-------------------+----------+--------------+------------------+
 
| File              | Position | Binlog_Do_DB | Binlog_Ignore_DB |
 
+-------------------+----------+--------------+------------------+
 
| servername.000001 |      329 |              |                  |
 
+-------------------+----------+--------------+------------------+
 
1 row in set (0.00 sec)

mysql 5.7.18

mysql> show master status;
 
+---------------------+----------+--------------+------------------+-------------------+
 
| File                | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
 
+---------------------+----------+--------------+------------------+-------------------+
 
| servername.dmz.corp |      154 |              |                  |                   |
 
+---------------------+----------+--------------+------------------+-------------------+
 
1 row in set (0,00 sec)

Comment by Oli Sennhauser [ 2017-12-06 ]

In MySQL the bug is as well but there it even destroys the binary logs and corrupts them...

Comment by Sergei Golubchik [ 2017-12-17 ]

This is the expected behavior. Documented, for example, here:

If you supply an extension in the log name (for example, --log-bin=base_name.extension), the extension is silently removed and ignored.

I've now documented it in the Knowledge Base too.

Generated at Thu Feb 08 08:14:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.