[MDEV-12418] --flashback server option does not force binlog_row_image Created: 2017-03-31 Updated: 2020-11-11 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Replication, Server |
| Affects Version/s: | 10.2.4 |
| Fix Version/s: | 10.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Kolbe Kegel (Inactive) | Assignee: | Andrei Elkin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Because Flashback requires binlog_row_image=FULL, the --flashback server option should set and force that value. Today, it's possible to set binlog_row_image to some other value in a different .cnf file, which would make the Flashback feature useless, even though an administrator may have started the server with --flashback enabled. Whether a user should still be able to dynamically change binlog_row_image I don't know. Maybe only with SUPER? |
| Comments |
| Comment by Elena Stepanova [ 2017-03-31 ] |
|
I'll leave it to plinux to decide. I'm not even sure that forcing binlog_format is such a good idea, it becomes messy and confusing when both options are provided explicitly. And yes, both can be re-defined at runtime anyway (binlog_format by a superuser, but binlog_row_image by anyone). |