Skip to main content

Timeline for How to manage binlog in MySQL?

Current License: CC BY-SA 4.0

13 events
when toggle format what by license comment
Dec 1, 2022 at 21:16 vote accept Niyaz
Dec 1, 2022 at 17:41 history edited Niyaz CC BY-SA 4.0
added 441 characters in body
Dec 1, 2022 at 16:32 answer added Bill Karwin timeline score: 3
Dec 1, 2022 at 7:40 history edited Niyaz CC BY-SA 4.0
added 33 characters in body
Dec 1, 2022 at 7:23 comment added Niyaz @BillKarwin I use ALTER TABLE table_name DROP PARTITION pname;
Dec 1, 2022 at 7:14 history edited Niyaz CC BY-SA 4.0
added 137 characters in body; edited title
Dec 1, 2022 at 2:37 comment added Bill Karwin How are you deleting partitions? They should not cause the binlog to expand a lot, because normally dropping partitions is done with ALTER TABLE, a DDL statement, which is always written to the binlog in statement format. Thus it should be small, not the size of the data in your partition. But if you use a DML statement like DELETE, and use ROW format for the binlogs, then that would expand the binlog proportional to the size of rows you delete.
Dec 1, 2022 at 0:31 comment added mustaccio Your question title literally says "How to disable (or manage) my binlog in MySQL?". Is that inaccurate?
Nov 30, 2022 at 21:46 review Close votes
Dec 23, 2022 at 3:06
Nov 30, 2022 at 21:32 comment added Niyaz My question is not about how to disable binlog. what I said is, besides replication is there any other cases that I need my binlog? or if there is any relation between PARTITION and binlog?
Nov 30, 2022 at 21:28 comment added mustaccio Does this answer your question? Disable MySQL binary logging with log_bin variable
Nov 30, 2022 at 21:27 comment added mustaccio If you don't need the binary log, why did you enable it in the first place? In any case, to disable it do the reverse.
Nov 30, 2022 at 21:05 history asked Niyaz CC BY-SA 4.0