« Show Previous 30 Entries | Showing 31-60 of 85 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
110232 | 2023-02-28 11:10 | 2023-03-01 12:43 | MySQL Server: Logging | Verified (432 days) | S3 | MySQL 8.0.32 | Ubuntu (22.04) | ARM | "Killed" counter is not updated with "log_slow_extra" enabled |
110130 | 2023-02-20 8:17 | 2023-02-20 8:26 | MySQL Server: Logging | Verified (441 days) | S3 | 8.0.32 | CentOS (7.9) | x86 | Wrong table-path in Error:1114 and Error:13132 |
110098 | 2023-02-16 11:57 | 2023-02-16 12:33 | MySQL Server: Logging | Verified (445 days) | S3 | Ver 8.0.32 | Any | Any | add database message into slow log file |
88404 | 2017-11-08 13:17 | 2017-11-08 14:02 | MySQL Server: Logging | Verified (2371 days) | S3 | 5.6/5.7/8.0 | Any | Any | Forcing close of thread XXX messages have extra new line in them. |
109552 | 2023-01-09 12:52 | 2023-01-09 13:40 | MySQL Server: Logging | Verified (483 days) | S3 | 5.7 | Any | Any | TRUNCATE TABLE causes "Stopping / Starting purge" log entries |
109482 | 2022-12-25 9:33 | 2022-12-26 4:56 | MySQL Server: Logging | Verified (497 days) | S3 | 8.0.27 | Any | Any | The mysql slow query log contains invalid content, and the mysql common log file |
107352 | 2022-05-20 11:00 | 2022-05-30 8:22 | MySQL Server: Logging | Verified (707 days) | S3 | 8.0.28, 8.0.29 | Any | Any | ROWS_EXAMINED confusing in MySQL 8 |
107224 | 2022-05-05 17:01 | 2022-09-19 9:19 | MySQL Server: Logging | Verified (731 days) | S3 | 8.0.29 | Any | Any | missleading Redo log format is error |
107000 | 2022-04-13 8:57 | 2022-04-13 9:41 | MySQL Server: Logging | Verified (754 days) | S3 | 8.0.25, 8.0.28 | Any | Any | Misspelling of words in error message |
106078 | 2022-01-06 6:36 | 2022-01-06 7:30 | MySQL Server: Logging | Verified (851 days) | S2 | 5.7.36 | Linux | Any | Incorrectly report "table doesn't exist" when FK columns are inconsistent |
105540 | 2021-11-12 7:10 | 2023-06-07 15:17 | MySQL Server: Logging | Verified (906 days) | S3 | 5.7,8.0 | Any | Any | the incorrect value of start_time field in the system table 'mysql.slow_log' |
105185 | 2021-10-11 8:36 | 2021-10-13 6:26 | MySQL Server: Logging | Verified (936 days) | S3 | 8.0.25 | Any | Any | log_queries_not_using_indexes does nothing for full index scan |
104929 | 2021-09-13 13:42 | 2021-09-13 14:02 | MySQL Server: Logging | Verified (966 days) | S3 | 8.0 | Any | Any | Contribution: Modify \'The table \'...\' is full message to indicate the co ... |
67903 | 2012-12-14 2:48 | 2012-12-14 16:54 | MySQL Server: Logging | Verified (4161 days) | S3 | mysql-5.5.28 | Linux | Any | Error return without giving a log message |
31102 | 2007-09-20 4:21 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (6068 days) | S3 | 5.1.22-rc, 5.1.21 | Linux | Any | set global general_log_file does not check that log file exists, can corrupt fil |
71842 | 2014-02-26 12:18 | 2014-03-10 8:39 | MySQL Server: Logging | Verified (3710 days) | S3 | 5.6.16 | Any | Any | Add P_S file instrumentation to the audit log plugin |
71599 | 2014-02-06 7:48 | 2014-07-31 13:28 | MySQL Server: Logging | Verified (3567 days) | S3 | 5.6.15, 5.6.19 | Any | Any | Unexpected log output for mysqld --help --verbose |
71462 | 2014-01-23 22:58 | 2016-03-24 10:40 | MySQL Server: Logging | Verified (3752 days) | S3 | 5.7.3, 5.6.17, 5.5.35 | Linux | Any | mysqld_safe does not cooperate with log rotation when logging to a file |
71377 | 2014-01-14 17:31 | 2014-01-17 7:29 | MySQL Server: Logging | Verified (3762 days) | S3 | 5.1+, 5.6.15 | Any | Any | too larege examined_row_count prevents logging mysql.slow_log |
71067 | 2013-12-04 0:26 | 2016-02-25 12:24 | MySQL Server: Logging | Verified | S3 | 5.7.3 | Any | Any | GQL does not log COM_RESET_CONNECTION |
70736 | 2013-10-26 18:11 | 2014-06-01 15:28 | MySQL Server: Logging | Verified (3627 days) | S3 | 5.6.14 | Any | Any | Warning about missing RSA keypair is wrong |
70428 | 2013-09-26 3:40 | 2013-09-30 3:58 | MySQL Server: Logging | Verified (3871 days) | S3 | 5.6, 5.7 | Any | Any | function find_uniq_filename can be optimized |
70296 | 2013-09-11 9:04 | 2013-09-11 11:50 | MySQL Server: Logging | Verified (3890 days) | S3 | 5.6.13 | Any | Any | replication errors are reported inconsistently |
69970 | 2013-08-09 7:00 | 2020-09-16 5:09 | MySQL Server: Logging | Verified (3920 days) | S3 | 5.5.33 | Any | Any | Can't restore a mysqldump if --add-drop-database meets general_log |
71879 | 2014-02-28 12:53 | 2014-03-06 13:00 | MySQL Server: Logging | Verified (3714 days) | S3 | 5.6.16, 5.6.17 | Any | Any | Wrong binlog size reported after moving binlogs |
63548 | 2011-12-02 19:13 | 2011-12-05 8:06 | MySQL Server: Logging | Verified (4539 days) | S3 | any | Any | Any | disable logging to slow log session-wise |
62908 | 2011-10-24 11:47 | 2011-10-25 9:18 | MySQL Server: Logging | Verified (4578 days) | S3 | 5.1+ | Any | Any | User may create tables with names reserved for log tables |
59847 | 2011-01-31 14:32 | 2014-09-22 20:50 | MySQL Server: Logging | Verified (4791 days) | S3 | 5.1.49-enterprise-gpl-pro-log | Linux (2.6.18-238.1.1.el5) | Any | Error closing the general/query logfile, if file is a named pipe/socket/fifo |
57690 | 2010-10-24 10:47 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (4917 days) | S3 | 5.1.50 | Linux | Any | impossible to redirect log-error to STDOUT in 5.1 |
54646 | 2010-06-20 21:41 | 2011-02-16 23:44 | MySQL Server: Logging | Verified (5068 days) | S3 | 5.1.47, 5.1.48 | Any | Any | SHOW PROFILES doesn't work for UPDATEs with triggers |
« Show Previous 30 Entries | Showing 31-60 of 85 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |