| Showing 1-30 of 85 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 31102 | 2007-09-20 4:21 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (6048 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 |
| 39618 | 2008-09-23 21:56 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (5620 days) | S3 | 5.0.27, 5.0.67 | Windows (XP) | Any | Using log-short-format does not change what is logged |
| 39775 | 2008-10-01 14:39 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (5675 days) | S3 | 6.0.8,6.0 bzr,5.4 | Any | Any | DBUG problems in 6.0 |
| 43395 | 2009-03-04 23:10 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (5522 days) | S3 | 5.1.30,6.0.5 | Any | Any | SQL Statements are logged in server query log |
| 50954 | 2010-02-05 19:46 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (5183 days) | S3 | MySQL 5.1.32, 5.1, 5.5.99 | Linux (Red Hat 4.1.2-44) | Any | start_time in slow query log is recording the query end time, not start time |
| 51629 | 2010-03-02 9:27 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (5159 days) | S3 | 5.1.44 | Any | Any | No good way to find the location of the binary log. |
| 54646 | 2010-06-20 21:41 | 2011-02-16 23:44 | MySQL Server: Logging | Verified (5048 days) | S3 | 5.1.47, 5.1.48 | Any | Any | SHOW PROFILES doesn't work for UPDATEs with triggers |
| 57690 | 2010-10-24 10:47 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (4897 days) | S3 | 5.1.50 | Linux | Any | impossible to redirect log-error to STDOUT in 5.1 |
| 59847 | 2011-01-31 14:32 | 2014-09-22 20:50 | MySQL Server: Logging | Verified (4771 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 |
| 62908 | 2011-10-24 11:47 | 2011-10-25 9:18 | MySQL Server: Logging | Verified (4558 days) | S3 | 5.1+ | Any | Any | User may create tables with names reserved for log tables |
| 63548 | 2011-12-02 19:13 | 2011-12-05 8:06 | MySQL Server: Logging | Verified (4519 days) | S3 | any | Any | Any | disable logging to slow log session-wise |
| 67903 | 2012-12-14 2:48 | 2012-12-14 16:54 | MySQL Server: Logging | Verified (4141 days) | S3 | mysql-5.5.28 | Linux | Any | Error return without giving a log message |
| 69970 | 2013-08-09 7:00 | 2020-09-16 5:09 | MySQL Server: Logging | Verified (3900 days) | S3 | 5.5.33 | Any | Any | Can't restore a mysqldump if --add-drop-database meets general_log |
| 70296 | 2013-09-11 9:04 | 2013-09-11 11:50 | MySQL Server: Logging | Verified (3870 days) | S3 | 5.6.13 | Any | Any | replication errors are reported inconsistently |
| 70428 | 2013-09-26 3:40 | 2013-09-30 3:58 | MySQL Server: Logging | Verified (3851 days) | S3 | 5.6, 5.7 | Any | Any | function find_uniq_filename can be optimized |
| 70736 | 2013-10-26 18:11 | 2014-06-01 15:28 | MySQL Server: Logging | Verified (3607 days) | S3 | 5.6.14 | Any | Any | Warning about missing RSA keypair is wrong |
| 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 |
| 71377 | 2014-01-14 17:31 | 2014-01-17 7:29 | MySQL Server: Logging | Verified (3742 days) | S3 | 5.1+, 5.6.15 | Any | Any | too larege examined_row_count prevents logging mysql.slow_log |
| 71462 | 2014-01-23 22:58 | 2016-03-24 10:40 | MySQL Server: Logging | Verified (3732 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 |
| 71599 | 2014-02-06 7:48 | 2014-07-31 13:28 | MySQL Server: Logging | Verified (3547 days) | S3 | 5.6.15, 5.6.19 | Any | Any | Unexpected log output for mysqld --help --verbose |
| 71842 | 2014-02-26 12:18 | 2014-03-10 8:39 | MySQL Server: Logging | Verified (3690 days) | S3 | 5.6.16 | Any | Any | Add P_S file instrumentation to the audit log plugin |
| 71879 | 2014-02-28 12:53 | 2014-03-06 13:00 | MySQL Server: Logging | Verified (3694 days) | S3 | 5.6.16, 5.6.17 | Any | Any | Wrong binlog size reported after moving binlogs |
| 72187 | 2014-04-01 13:34 | 2014-04-04 19:42 | MySQL Server: Logging | Verified (3665 days) | S3 | 5.6.16 | Any | Any | Crash with 5.5 datadir |
| 72243 | 2014-04-04 18:48 | 2014-04-04 19:33 | MySQL Server: Logging | Verified (3665 days) | S3 | 5.7.4 | Any | Any | Queries where execution time exceeds 'MAX_STATEMENT_TIME' should go to slow log |
| 72464 | 2014-04-26 10:12 | 2014-04-29 8:12 | MySQL Server: Logging | Verified | S3 | 5.6.17 | Any | Any | the unsafe statement spam throttling is not good enough |
| 72529 | 2014-05-04 10:13 | 2014-05-04 11:22 | MySQL Server: Logging | Verified (3635 days) | S5 | 5.5 | Any | Any | rm a large slow log file and then flush slow logs, the mysqld will hang |
| 72598 | 2014-05-09 21:54 | 2014-06-18 6:06 | MySQL Server: Logging | Verified (3591 days) | S3 | 5.1, 5.5 | Linux (syslog-capable) | Any | FLUSH LOGS fails with error 1105 if both syslog and log-error are enabled |
| 73750 | 2014-08-28 8:13 | 2014-08-28 9:48 | MySQL Server: Logging | Verified (3519 days) | S3 | 5.6.20, all? | Linux | Any | mysqld_multi writes logfile to wrong directory |
| 73920 | 2014-09-15 10:34 | 2017-05-10 10:32 | MySQL Server: Logging | Verified (2748 days) | S2 | 5.6.20, 5.6.22, 5.7.6, 5.6.23 | Any | Any | [ERROR] Invalid (old?) table or database name 'xyz' |
| 74145 | 2014-09-29 22:05 | 2014-09-30 12:18 | MySQL Server: Logging | Verified (3486 days) | S3 | 5.5.39, 5.5.41 | Linux | Any | FLUSH LOGS improperly disables the logging if the log file cannot be accessed |
| Showing 1-30 of 85 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
