-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Too many error log printed #12114
Comments
Relates to #18566 This can be a security risk, since these statements are logged verbatim. |
Another example mysql> set tidb_mem_quota_query=1;
Query OK, 0 rows affected (0.00 sec)
mysql> select 1 union select 2;
ERROR 1105 (HY000): Out Of Memory Quota![conn_id=1] It produces 5 lines log.
|
We should probably just change the logging level of application-facing errors so they aren't written to the server error log, or to make it easy for a user to toggle that. There isn't much use in writing duplicate key and syntax errors to the server log, those are not problems a DBA should usually be concerned with. Those errors are returned to the client, which is responsible in any case for handling them. |
I like how performance_schema in MySQL 8.0 instruments client errors. It can be useful after an upgrade, change to sql-mode etc. Not all applications track this as they are expected. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
If possible, provide a recipe for reproducing the error.
One line log with enough information.
3 line log with huge and redundant information.
tidb-server -V
or runselect tidb_version();
on TiDB)?c1d5536
The text was updated successfully, but these errors were encountered: