Pandikrishnan Gurusamy added a comment - 2024-02-28 10:07 The variable log_warnings is also stated as session level by when changing the variable session-level. It doesn't log for the connection changed for the session level. In the below example, the connection id 67 was not logged in the error log. MariaDB [(none)]> select @@log_warnings; +----------------+ | @@log_warnings | +----------------+ | 2 | +----------------+ 1 row in set (0.002 sec)   MariaDB [(none)]> set log_warnings=9; Query OK, 0 rows affected (0.000 sec)   MariaDB [(none)]> show processlist; +----+------+-----------+------+---------+------+----------+------------------+----------+ | Id | User | Host | db | Command | Time | State | Info | Progress | +----+------+-----------+------+---------+------+----------+------------------+----------+ | 67 | root | localhost | NULL | Query | 0 | starting | show processlist | 0.000 | +----+------+-----------+------+---------+------+----------+------------------+----------+ 1 row in set (0.000 sec)   MariaDB [(none)]> kill 67; ERROR 1927 (70100): Connection was killed MariaDB [(none)]> show global variables like 'log%war%'; ERROR 2006 (HY000): Server has gone away No connection. Trying to reconnect... Connection id: 68 Current database: *** NONE ***

Sergei Golubchik added a comment - 2024-02-28 17:03 Thanks! Documentation is updated.

Pandikrishnan Gurusamy added a comment - 2024-02-29 00:54 Thanks serg . Our doc also states log_warnings is a session-level variable, but it doesn't take any effect for session-level changes. Pls, find the first comment in this ticket.

Sergei Golubchik added a comment - 2025-01-24 15:20 - edited "Aborted connection" warning is controlled by the global value of log_warnings, any session changes won't affect it. Other warnings are affected by it, though