Details
-
New Feature
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Do
Description
Can we keep MariaDB (relatively) aligned to the MySQL's behavior on SIGHUP & SIGUSR1?
I've tested w/ MariaDB 10.11 and
- for SIGHUP - after MySQL 8.0.20 the server does not write anymore the status report in the error log file, MariaDB still does - not taking sides on this one - in my opinion it is debatable if that output can be considered an "error.log", more like a candidate for "general.log", but I wouldn't suppress it completely either;
- for SIGUSR1 - this exists with MySQL 8.0.19 and newer, MariaDB ignores this.
The latter SIGUSR1 is useful for log file rotation as it covers a subset of the operations done in SIGHUP.
Also the same mechanism is used by others (example: Nginx rotates logs at SIGUSR1).