-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable MariaDB binary log #1881
Conversation
This resolves a warning in the database server log: [Warning] You need to use --log-bin to make --binlog-format work. Pros: * support for point-in-time recovery * necessary for replication Cons: * slows down database operations ("slightly", per the manual) * takes up disk space (mitigated by `--expire-logs-days=2`) See also: * <https://mariadb.com/kb/en/binary-log/> * <https://mariadb.com/kb/en/full-list-of-mariadb-options-system-and-status-variables/> Alternatives: 1. Do not add `--log-bin`. Remove `--binlog-format` instead. This causes the least amount of change for existing installations. Signed-off-by: Adam Monsen <[email protected]>
We use the recommend parameters from here:
Are you familiar with those parameters? I wonder if this would also affect everyone else using MariaDB/MySQL. If so, this should probably be discussed in the upstream documentation:
|
Thank you, I reviewed those sections of documentation. The first one recommends either using a row-level binary log or disabling the binary log. The second one (with the example My patch is mostly coherent with the documentation, and it fixes the MariaDB warning. I anticipate the impact of the change will be minimal and positive. To better align with recommendations in the Nextcloud documentation, I'll remove |
This better aligns with recommendations in the Nextcloud documentation. Also: the flag isn't necessary. There are already set times for cleanup: The MySQL and MariaDB documentation both state that binary logs will be purged on startup and flush/rotation. Signed-off-by: Adam Monsen <[email protected]>
7043075
to
ad39450
Compare
* Enable MariaDB binary log This resolves a warning in the database server log: [Warning] You need to use --log-bin to make --binlog-format work. Pros: * support for point-in-time recovery * necessary for replication Cons: * slows down database operations ("slightly", per the manual) * takes up disk space (mitigated by `--expire-logs-days=2`) See also: * <https://mariadb.com/kb/en/binary-log/> * <https://mariadb.com/kb/en/full-list-of-mariadb-options-system-and-status-variables/> Alternatives: 1. Do not add `--log-bin`. Remove `--binlog-format` instead. This causes the least amount of change for existing installations. Signed-off-by: Adam Monsen <[email protected]> * remove --expire-logs-days=2 mariadb flag This better aligns with recommendations in the Nextcloud documentation. Also: the flag isn't necessary. There are already set times for cleanup: The MySQL and MariaDB documentation both state that binary logs will be purged on startup and flush/rotation. Signed-off-by: Adam Monsen <[email protected]> --------- Signed-off-by: Adam Monsen <[email protected]>
This resolves a warning in the database server log:
Pros:
Cons:
--expire-logs-days=2
)See also:
Alternatives:
--log-bin
. Remove--binlog-format
instead. This causes the least amount of change for existing installations.Signed-off-by: Adam Monsen [email protected]