Showing 1-30 of 93 (Edit, Save, CSV, Feed) Show Next 30 Entries »
ID# Date Updated Type Status Sev Version OS CPU Summary
1035352021-04-29
13:57
2021-04-30
6:38
MySQL Server: Command-line ClientsVerified
(52 days)
S35.7.34, 8.0.24AnyAnyshow warnings non empty after Lost connection to MySQL server during query.
715272014-01-30
15:19
2014-02-06
11:51
MySQL ServerClosed
(2692 days)
S25.6.15 & 5.7.3AnyAnyWith GTID_MODE=ON, anonymous transactions are assigned local GTIDs on slaves.
914552018-06-28
8:34
2018-06-29
4:53
MySQL ServerDuplicate
(1088 days)
S4LinuxAnyImplement core dump size reduction.
920242018-08-15
17:48
2018-11-02
17:53
MySQL Server: Connection HandlingClosed
(962 days)
S35.7.23, 8.0.12, 5.6.41AnyAnySetting thread_cache_size to 0 does not empty the Thread Cache.
1031162021-03-25
20:34
2021-03-26
18:47
MySQL Server: DDLVerified
(87 days)
S48.0.23, 5.7.33AnyAnyMake removing an auto-increment on a table a meta-data only ALTER.
986232020-02-16
13:46
2020-02-17
6:13
MySQL Server: DDLVerified
(490 days)
S45.7.29, 8.0.19AnyAnyPlease make adding/removing AUTO_INCREMENT to a table efficient.
859772017-04-18
2:02
2018-11-02
15:03
MySQL Server: DocumentationVerified
(1525 days)
S35.7 and 8.0AnyAnyThe doc. of slave-parallel-type=LOGICAL_CLOCK wrongly reference Group Commit.
826672016-08-20
11:19
2018-08-31
10:53
MySQL Server: DocumentationClosed
(1038 days)
S35.6 and 5.7 documentationsAnyAnyPlease clarify resiliency introduced by master_info_repository to TABLE.
920122018-08-14
14:47
2018-08-15
21:59
MySQL Server: DocumentationClosed
(1041 days)
S38.0, 5.7, 5.6AnyAnyWrong default for thread_cache_size in "How MySQL Uses Threads for Client Cnx".
753952015-01-02
14:46
2018-07-25
17:16
MySQL Server: DocumentationClosed
(1062 days)
S45.7.5AnyAnyExplain relation between slave_preserve_commit_order and binlog_order_commit.
753942015-01-02
14:45
2019-01-24
10:53
MySQL Server: DocumentationClosed
(879 days)
S45.6 and 5.7AnyAnyImprove documentation of binlog_order_commits.
920642018-08-18
18:39
2018-08-31
12:09
MySQL Server: DocumentationClosed
(1025 days)
S35.6, 5.7, 8.0AnyAnyInformation for the recovery of the IO thread is NOT in mysql.slave_master_info.
973982019-10-28
13:57
2019-11-05
15:49
MySQL Server: DocumentationClosed
(594 days)
S35.7AnyAnyWrong documentation for innodb_max_purge_lag.
1018742020-12-05
1:29
2020-12-07
18:26
MySQL Server: DocumentationVerified
(198 days)
S25.7.32, 8.0.16AnyAnyThe manual is missing sync_binlog = 1 for GTID replication crash safety.
1018762020-12-05
4:05
2020-12-05
7:02
MySQL Server: DocumentationVerified
(198 days)
S35.7, 8.0AnyAnyThe manual is overly conservative in parameters for replication crash safety.
730382014-06-18
14:14
2014-07-08
11:52
MySQL Server: DocumentationClosed
(2540 days)
S35.6.19AnyAnyBetter document (or fix) relay_log_recovery.
920932018-08-20
21:24
2019-09-04
15:15
MySQL Server: DocumentationClosed
(656 days)
S25.7.23AnyAnyReplication crash safety needs relay_log_recovery even with GTID.
1030622021-03-22
16:07
2021-04-06
12:33
MySQL Server: DocumentationVerified
(76 days)
S3AnyAnyMySQL Replication extract from 5.7 is non-consistent with Reference Manual.
741112014-09-26
16:01
2014-12-03
15:20
MySQL Server: ErrorsClosed
(2428 days)
S35.7.5/5.6Linux (CentOS 6.5)AnyWhen the socket option is relative, mysqld startup script fails on CentOS 6.
845782017-01-20
9:53
2017-01-21
8:01
MySQL Server: ErrorsVerified
(1612 days)
S45.6 and 5.7AnyAnyAdd a SHOW WARNINGS SUMMARY function.
845572017-01-18
16:50
2017-01-19
19:07
MySQL Server: ErrorsVerified
(1614 days)
S45.6 and 5.7AnyAnyHide specific warnings from SHOW WARNINGS.
891462018-01-08
22:16
2018-06-20
16:45
MySQL Server: Group ReplicationClosed
(1097 days)
S35.7.20, 8.0.3AnyAnyBinlog name and Pos are wrong in group_replication_applier channel's error msgs
891412018-01-08
22:07
2018-04-11
16:23
MySQL Server: Group ReplicationDuplicate
(1167 days)
S25.7.20,8.0.3AnyAnyError in Group Replication caused by bad Write Set tracking.
891422018-01-08
22:09
2019-04-30
15:41
MySQL Server: Group ReplicationClosed
(783 days)
S45.7.20, 8.0.3AnyAnyMake FLUSH RELAY LOGS work for Group Replication.
891452018-01-08
22:15
2018-01-11
9:47
MySQL Server: Group ReplicationVerified
(1257 days)
S45.7.20,8.0.3AnyAnyProvide relay log details in case of Group Replication applier failure.
891472018-01-08
22:18
2018-01-11
9:52
MySQL Server: Group ReplicationVerified
(1257 days)
S45.7.20,8.0.3AnyAnyThe field end_log_pos in Group Replication error messages is ambiguous.
891482018-01-08
22:23
2019-06-04
1:24
MySQL Server: Group ReplicationVerified
(1225 days)
S45.7.20 and 8.0.3AnyAnyThe timestamp of the GITD events in the GR relay log look wrong.
891942018-01-11
19:14
2018-04-11
16:23
MySQL Server: Group ReplicationDuplicate
(1167 days)
S25.7.20, 8.0.3AnyAnyWrong certification lead to data inconsistency and GR breakage.
891952018-01-11
19:15
2019-07-25
14:45
MySQL Server: Group ReplicationClosed
(697 days)
S25.7.20, 8.0.3AnyAnyTotal ordering of transactions is not respected in Group Replication.
954782019-05-22
15:31
2019-05-23
13:36
MySQL Server: InnoDB storage engineVerified
(760 days)
S45.7.26AnyAnyCREATE TABLE LIKE does not honour ROW_FORMAT.
  Showing 1-30 of 93 (Edit, Save, CSV, Feed) Show Next 30 Entries »