Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.0.14
-
None
Description
I noticed MariaDB does not have corresponding MySQL system variables:
log_bin_basename and log_bin_index
Without log_bin_basename, there is no way to tell the location and name of the binary log.
This is easily identifiable in MySQL:
mysql> show global variables like 'log_bin%'; |
+---------------------------------+---------------------------------------------------------------------+ |
| Variable_name | Value |
|
+---------------------------------+---------------------------------------------------------------------+ |
| log_bin | ON | |
| log_bin_basename | C:\Program Files\MySQL\MySQL Server 5.6\Data\chris-laptop-bin |
|
| log_bin_index | C:\Program Files\MySQL\MySQL Server 5.6\Data\chris-laptop-bin.index | |
Without these, you can only conform whether binlogging is enabled or not.
Attachments
Issue Links
- blocks
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
MDEV-5277 Ensure that all MySQL 5.6 options are supported by the MariaDB 10.0 server
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
I noticed MariaDB does not have corresponding MySQL system variables: log_bin_basename and log_bin_index Without log_bin_basename, there is no way to tell the location and name of the binary log. This is easily identifiable in MySQL: mysql> show global variables like 'log_bin%'; +---------------------------------+---------------------------------------------------------------------+ | Variable_name | Value | +---------------------------------+---------------------------------------------------------------------+ | log_bin | ON | | log_bin_basename | C:\Program Files\MySQL\MySQL Server 5.6\Data\chris-laptop-bin | | log_bin_index | C:\Program Files\MySQL\MySQL Server 5.6\Data\chris-laptop-bin.index | Without these, you can only conform whether binlogging is enabled or not. |
I noticed MariaDB does not have corresponding MySQL system variables: log_bin_basename and log_bin_index Without log_bin_basename, there is no way to tell the location and name of the binary log. This is easily identifiable in MySQL: {code:sql} mysql> show global variables like 'log_bin%'; +---------------------------------+---------------------------------------------------------------------+ | Variable_name | Value | +---------------------------------+---------------------------------------------------------------------+ | log_bin | ON | | log_bin_basename | C:\Program Files\MySQL\MySQL Server 5.6\Data\chris-laptop-bin | | log_bin_index | C:\Program Files\MySQL\MySQL Server 5.6\Data\chris-laptop-bin.index | {code} Without these, you can only conform whether binlogging is enabled or not. |
log-bin-basename is actually listed in MDEV-5277, in the last section "NO_CMD_LINE options", which are said not to be added.
Assigning to svoj who can probably remember why it was decided not to add it, and comment on log_bin_index as well.
| Assignee | Sergey Vojtovich [ svoj ] |
MDEV-5277 was supposed to add missing command line options. While these options have NO_CMD_LINE flag, which means they're just system variables without corresponding command line.
MySQL revision-id is mats.kindahl@oracle.com-20101104144352-z7dy7e46jlexdfnw
They should probably be added indeed.
| Assignee | Sergey Vojtovich [ svoj ] | Kristian Nielsen [ knielsen ] |
knielsen, could you take this? Upstream patch is a bit more than just adding log_bin_basename and log_bin_index. I'm not sure if those changes are valuable.
| Assignee | Kristian Nielsen [ knielsen ] | Nirbhay Choubey [ nirbhay_c ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Fix Version/s | 10.1 [ 16100 ] |
| Status | In Progress [ 3 ] | Stalled [ 10000 ] |
| Status | Stalled [ 10000 ] | In Progress [ 3 ] |
| Attachment | MDEV-7110_KB_v1.txt [ 38036 ] |
| Assignee | Nirbhay Choubey [ nirbhay_c ] | Kristian Nielsen [ knielsen ] |
| Status | In Progress [ 3 ] | In Review [ 10002 ] |
| Workflow | MariaDB v2 [ 58455 ] | MariaDB v3 [ 65299 ] |
| Assignee | Kristian Nielsen [ knielsen ] | Nirbhay Choubey [ nirbhay_c ] |
Patch:
https://github.com/MariaDB/server/commit/f965cae5fb04a9fd06a939a8f2b52228a62ce9fa
KB entries:
- https://mariadb.com/kb/en/mariadb/replication-and-binary-log-server-system-variables/#log_bin_basename
- https://mariadb.com/kb/en/mariadb/replication-and-binary-log-server-system-variables/#log_bin_index
- https://mariadb.com/kb/en/mariadb/replication-and-binary-log-server-system-variables/#relay_log_basename
| Component/s | Replication [ 10100 ] | |
| Fix Version/s | 10.1.6 [ 19401 ] | |
| Fix Version/s | 10.1 [ 16100 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10002 ] | Closed [ 6 ] |
| Link |
This issue relates to |
| Workflow | MariaDB v3 [ 65299 ] | MariaDB v4 [ 148471 ] |
These variables were not listed in the report below, and it is "closed", hence this new bug report:
https://mariadb.atlassian.net/browse/MDEV-5277