Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2.4
-
None
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?
Attachments
Issue Links
- is duplicated by
-
MDEV-18037 mysqld --flashback option should set binlog_row_image=FULL
-
- Closed
-
- relates to
-
MDEV-23746 Warnings about memory lost after using --flashback server option with binlog_row_image="minimal"
-
- Stalled
-
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | Replication [ 10100 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Assignee | Lixun Peng [ plinux ] |
Assignee | Lixun Peng [ plinux ] | Andrei Elkin [ elkin ] |
Link | This issue relates to MDEV-23746 [ MDEV-23746 ] |
Link |
This issue is duplicated by |
Workflow | MariaDB v3 [ 80209 ] | MariaDB v4 [ 140269 ] |
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).