« Show Previous 1000 Entries | Showing 1001-2000 of 2829 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
6016 | 2004-10-11 11:38 | 2004-10-11 14:47 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7109 days) | S2 | Any | Strange crash with blobs + different DATABASES | ||
9618 | 2005-04-04 18:16 | 2005-04-06 9:55 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6932 days) | S2 | 4.1.11 | x86: Linux, OpenBSD, QNX, Sol 8 | Any | Test 'group_by' returns more rows than expected when NDB is included |
11004 | 2005-05-31 22:11 | 2005-06-05 9:29 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6872 days) | S2 | 5.1.0 | Linux (Linux) | Any | 4 Data Node cluster does not survive a single node failure under load |
11366 | 2005-06-15 22:57 | 2005-09-14 18:52 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6771 days) | S2 | 5.1.0-wl2325-wl1354-new | Linux (Linux) | Any | mysqld process cores if cluster dies during SQL thread catch-up to master phase |
12114 | 2005-07-22 14:38 | 2005-08-01 16:45 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6815 days) | S3 | 5.1.0 | Linux (RHEL) | Any | Wrong node group in partition leads to table name not reusable in MySQL Cluster |
12395 | 2005-08-05 9:58 | 2005-08-11 13:35 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (6805 days) | S1 | 5.0 | Linux (Linux RH9) | Any | Crash in close_scan |
12594 | 2005-08-16 9:50 | 2014-03-13 13:34 | MySQL Cluster: Cluster (NDB) storage engine | Won't fix (6764 days) | S2 | 5.1 | Linux (RH9) | Any | Error while reading the REDO log |
13081 | 2005-09-09 7:36 | 2005-10-05 23:53 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6750 days) | S2 | 5.0.13 | Any | NDB gets incorrect result in test-ATIS | |
13826 | 2005-10-07 1:49 | 2006-01-10 10:10 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6653 days) | S2 | 5.1-ndb-dd | Linux (Linux) | Any | Crash when creating undofile /tmp/undofile.dat |
15530 | 2005-12-06 16:48 | 2006-04-20 6:20 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6553 days) | S3 | 4.1.26, 5.0.20, 5.1.2 | Linux (Linux) | Any | Cluster start up "show" shows all data nodes as master during start |
15531 | 2005-12-06 16:54 | 2006-06-08 7:20 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (6504 days) | S3 | 4.1 -> | Linux (Linux) | Any | Strange group numbers show on second node started (same host) during start |
16267 | 2006-01-06 22:01 | 2006-01-20 16:18 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6643 days) | S3 | 5.1.5 | Linux (Linux) | Any | DD: msg: Failed to create UNDOFILE needs to be changed |
16556 | 2006-01-17 2:14 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (6646 days) | S4 | mysql-5.1 | Any | Any | DD: New error messages needed |
16658 | 2006-01-20 0:26 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6612 days) | S3 | 5.1 | Linux (Linux) | Any | DD: ALTERing LG that does not exist produces error 1064 |
16768 | 2006-01-25 3:33 | 2006-02-07 5:52 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6625 days) | S3 | 5.1 | Linux (Linux) | Any | DD: DROP LG that does not exist returns wrong error code |
16787 | 2006-01-25 17:00 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6602 days) | S3 | 5.1 | Linux (Linux) | Any | DD: CREATE LG with INITIAL_SIZE 3G returns error after 40 min. |
17594 | 2006-02-20 19:41 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6559 days) | S1 | 5.1.7-beta | Various Unix | Any | Various NDB startup / restart problems |
17999 | 2006-03-06 22:35 | 2006-05-24 19:52 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6519 days) | S2 | 5.1 | Linux (Linux) | Any | DD: Restore db to the directory that does not exist fails with unknown error. |
18000 | 2006-03-06 22:48 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6560 days) | S3 | 5.1.8 | Linux (Linux 32 Bit OS) | Any | DD: New test now takes 100X more space, reports out of space and cores NDBD |
18007 | 2006-03-07 1:20 | 2006-04-09 12:41 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6564 days) | S2 | 5.1.8-bk-20060305 | Linux (SuSE 10.0) | Any | SELECT * FROM I_S.FILES on mysqld on same host as data node crashes mysqld |
18295 | 2006-03-17 8:25 | 2006-03-27 12:07 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6577 days) | S1 | 5.1.8 | Linux (Linux 32 Bit OS) | Any | DD: DROP LOGFILE GROUP causes ndbd core when compiled with GCC4 |
18451 | 2006-03-23 8:46 | 2006-06-19 12:56 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6493 days) | S1 | 5.1 | Any | Restoring a backup changes fragement type | |
18593 | 2006-03-28 23:15 | 2006-05-23 22:11 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (6520 days) | S2 | 5.1.9 | Linux (Linux 32 Bit OS) | Any | Backup started from 1 has been aborted. Error: 723 |
18594 | 2006-03-28 23:25 | 2006-04-22 14:30 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6551 days) | S1 | 5.1.9 | Linux (Linux 32 Bit OS) | Any | ndb_restore log boken in 5.1 |
4126 | 2004-06-14 15:03 | 2004-08-20 9:54 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7161 days) | S1 | mysqlcluster-4.1.2-3.4.9-alpha-pc-linux- | Linux (Redhat AS) | Any | Node crashes when Data usage increased to 100% |
80554 | 2016-02-29 9:43 | 2016-04-26 5:53 | MySQL Cluster: Cluster (NDB) storage engine | Closed (2921 days) | S3 | 7.4.11 | Any | Any | Binlog schema distribution timeout and fails when another mysql node start |
22316 | 2006-09-13 15:49 | 2006-10-26 17:22 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6364 days) | S1 | 5.0.24a | Linux (CentOS 4.4 x86_64) | Any | Four-node cluster loses Node Group 1 |
99436 | 2020-05-04 11:51 | 2020-09-28 14:46 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (1278 days) | S3 | 8.0.20 | Red Hat (8) | Any | NDB fully replicated tables only in node group 0, not in node group 1 |
7718 | 2005-01-06 21:59 | 2014-03-13 13:33 | MySQL Cluster: Cluster (NDB) storage engine | Won't fix (7018 days) | S3 | 4.1.9 | Linux (Fedora Core 1) | Any | NDB Fails On Loading Complex Data Warehouse |
16738 | 2006-01-24 1:46 | 2006-01-26 0:45 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6637 days) | S1 | 5.1.6-alpha | Linux (Linux) | Any | DD: Cluster does not handle running out of space in disk data file |
19141 | 2006-04-17 15:43 | 2006-04-23 1:15 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6550 days) | S2 | 5.1.10 | Linux (Linux 32 Bit OS) | Any | DD: CREATE LFG during DROP of a NDB table cause DN failure and corruption |
7733 | 2005-01-07 16:36 | 2005-01-07 23:09 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (7021 days) | S3 | 4.1.9 | Linux (Fedora Core 1) | Any | [mysql_cluster] section connect-string confusion |
81760 | 2016-06-07 20:27 | 2016-08-09 14:52 | MySQL Cluster: Cluster (NDB) storage engine | Closed (2846 days) | S3 | 7.5.2 | Any | Any | Rename RealFragment to Partition in Ndb kernel code. |
66045 | 2012-07-27 10:28 | 2012-08-28 1:00 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (4232 days) | S2 | 5.5.22-ndb-7.2.6 | Other (debian 5 (2.6.26-2-amd64)) | Any | 5.5.22-ndb-7.2.6 CREATE LOGFILE GROUP failed |
19234 | 2006-04-20 22:31 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6549 days) | S2 | 5.1.7-beta-win3/5.1BK | Windows (Windows 2000/Linux) | Any | ERROR 2013 (HY000): Lost connection to MySQL server during query |
19706 | 2006-05-11 6:50 | 2006-08-16 7:10 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6435 days) | S3 | 5.0.21 | Linux (RHEL4) | Any | 5.0.21 GCP Stop during COPY_GCI |
19911 | 2006-05-18 14:55 | 2008-02-28 8:38 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5874 days) | S1 | 5.1.10-beta | Solaris (Solaris 10 (x86)) | Any | ndb does not work on sol10 x86 |
20742 | 2006-06-28 2:02 | 2006-07-04 23:14 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6478 days) | S1 | 5.1 | Linux (Linux) | Any | Assertion in drop of ndb binlog events after node restart |
21059 | 2006-07-14 13:10 | 2006-08-17 8:51 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6434 days) | S1 | 5.1.11, 5.0.19 | Linux (Linux) | Any | Server crashes on join query with large dataset with NDB tables |
21213 | 2006-07-21 12:44 | 2006-09-06 11:05 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6414 days) | S2 | 4.1,5.0,5.1 | Linux (Linux 2.6.9-34.ELsmp #1 ) | Any | 3r: Node restart fails and causes other node to shutdown |
21272 | 2006-07-25 12:40 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6437 days) | S2 | MySQL cluster 5.0.22 | Linux (Linux 2.6.9-34.ELsmp #1 ) | Any | Network failure causes MySQL cluster to shut down |
21778 | 2006-08-22 9:38 | 2006-08-23 10:09 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (6428 days) | S2 | MySQL cluster 5.0.24 | Linux (Redhat Linux 2.6.9-34.ELsmp #1 ) | Any | Network glitch causes incorrect node to shutdown |
23951 | 2006-11-03 16:41 | 2007-11-19 12:11 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5975 days) | S2 | MySQL cluster 5.0.27 | Linux (Linux 2.6.9-34.ELsmp #1) | Any | The failure handling of node X ends up in an infinite loop |
24030 | 2006-11-07 1:51 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6321 days) | S1 | 5.0.24 | Linux (Linux (RHEL4)) | Any | NDBD receives signal 11 segmentation fault, cluster shuts down, cannot restart |
25710 | 2007-01-18 22:32 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (5495 days) | S2 | 5.1.14 | Linux (CentOS4.4 x86_64) | Any | Restarting data node _always_ requires --initial |
26931 | 2007-03-07 19:32 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5397 days) | S1 | mysql-5.1 | Linux (Linux x86_64) | Any | Cluster Crashed |
27434 | 2007-03-26 8:56 | 2007-04-02 11:20 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6206 days) | S3 | 4.1,5.0,5.1 | Any | Any | Incorrect handling of FragState in take-over during SR |
27750 | 2007-04-11 7:01 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6133 days) | S1 | 5.1.15 | Linux (RHEL 4 AS Upd 4 (64bit)) | Any | NDB Cluster 5.1.15 crashes with internal error pointing to ndbrequire |
27947 | 2007-04-19 8:02 | 2007-04-24 11:03 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (6184 days) | S2 | ver 14.12 Distrib 5.0.27 | Linux (pc-linux-gnu (i686)) | Any | message slogan found (please report a bug if you get this error code) (Unknown |
29021 | 2007-06-11 16:19 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5873 days) | S2 | 5.1.4-a_drop5p19 | Linux (2.6.18-8.el5) | Any | Cluster failure on node recovery. |
29167 | 2007-06-18 4:57 | 2007-06-23 7:03 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6124 days) | S3 | 5.0-wl2325-5.0, 5.1* | Any | Any | Insufficient nodes for SR |
30831 | 2007-09-05 12:27 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5778 days) | S3 | mysql-5.1 | Any | Any | All data nodes are listed in nodegroup 0 while starting |
31525 | 2007-10-11 9:49 | 2007-11-06 9:15 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5988 days) | S3 | 4.1,5.0,5.1 | Any | Any | Incorrect handling of ActiveMissed_2, potential "Lost node group" after SR |
33060 | 2007-12-07 12:18 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5608 days) | S1 | 5.1.22-rc | Linux (Debian 4.0, mysql from src) | Any | Crash on subselect with MAX() |
55611 | 2010-07-28 16:34 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (4933 days) | S2 | mysql-5.1-telco-6.3 | Solaris | Any | GCP stop was detected NDBCNTR (Line: 249) Solaris10 |
55802 | 2010-08-06 13:45 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (4984 days) | S4 | mysql-5.1-telco-7.1 | Any | Any | Unconvenient default settings for InitialLogFileGroup, InitialTablespace |
57563 | 2010-10-19 11:17 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (4909 days) | S2 | Linux | Any | m_gcp_rep_counter ring buffer capacity exceeded | |
58453 | 2010-11-24 11:13 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (4873 days) | S3 | Any | Any | Incorrectly handling of GSN_COMMIT/GSN_COMPLETE during take-over | |
60654 | 2011-03-26 10:47 | 2012-05-25 10:23 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (4326 days) | S1 | mysql-5.1.30 ndb-6.3.20-GA | Linux (Redhat 5) | Any | Error data: Killed by node 3 as copyfrag failed, error: 1501 |
65234 | 2012-05-08 6:51 | 2015-01-09 10:17 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3367 days) | S1 | NDB 7.2.5, MySQL 5.5.20 | Linux (Ubuntu 11.10 x64) | Any | Memcached crashes when use "caching" policy on get and without cas_column |
68151 | 2013-01-23 3:28 | 2016-07-18 16:30 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (2811 days) | S1 | 7.2.10 | Linux (generic x64 linux binary on ubuntu) | Any | Fresh 7.2.10 cluster rolling restart all datanodes crash in DBSPJ DbspjMain.cpp |
69851 | 2013-07-26 18:48 | 2013-07-29 14:27 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (3896 days) | S3 | 7.2.10 | Linux | Any | Unable to create undofile and/or data files after --initial restart |
71342 | 2014-01-10 14:37 | 2014-01-16 9:29 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (3725 days) | S2 | 7.3.2 | Solaris | Any | Alter ONLINE Table REORGAMIZE PARTITION asks for ALGORITHM=INPLACE |
73339 | 2014-07-21 9:54 | 2016-03-24 1:00 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (2928 days) | S1 | 7.3.6 | Linux (2.6.32) | Any | NDB data node crashes after upgrade from 7.2.13 to 7.3.5 - illegal signal |
73691 | 2014-08-22 22:55 | 2015-11-29 1:00 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (3044 days) | S2 | 7.3.5 | Linux (Red Hat EL 6.4) | Any | ndbd crash with segfault when missing DATAFILE |
74438 | 2014-10-18 16:42 | 2015-10-02 15:01 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (3101 days) | S1 | 7.3.6 | Linux (Red Hat(64-bit)) | Any | ndbd cannot be started caused by error 2807 |
80582 | 2016-03-02 9:59 | 2016-05-12 5:18 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2878 days) | S3 | mysql-cluster-7.4.7 | Linux | Any | Loose index scans not supported by ndbcluster engine? |
112400 | 2023-09-20 17:18 | 2023-09-25 3:58 | MySQL Cluster: Cluster (NDB) storage engine | Verified (186 days) | S3 | 8.0.34 | Any | Any | Reading non-readable node |
40724 | 2008-11-14 2:08 | 2013-10-06 20:45 | MySQL Cluster: Disk Data | Duplicate (5517 days) | S1 | 6.3.18 | Linux (Ubuntu 8.10) | Any | Entire Cluster Crashes When A LG With Large Undo Log >150M Is Created |
40921 | 2008-11-21 10:39 | 2011-02-16 23:43 | MySQL Cluster: Disk Data | Closed (5607 days) | S3 | Any | Any | Incorrectly handle resource shortage during create/drop DD object | |
51045 | 2010-02-09 22:58 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Duplicate (5156 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | Creating an UNDO log fails without error |
53108 | 2010-04-23 11:45 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified (5089 days) | S3 | mysql-5.1-telco-7.0 | Linux | Any | Log group and table space create info not filtered out by "mysqldump --no-create |
80867 | 2016-03-28 12:17 | 2016-05-04 5:01 | MySQL Cluster: Disk Data | Not a Bug (2886 days) | S1 | 7.4.10 | Debian (Wheezy) | Any | MySQL Cluster Crashed |
31714 | 2007-10-19 11:35 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified (5999 days) | S3 | mysql-5.1 | Linux | Any | No usefull feedback when trying to create tablespace with nonexistant log group |
31772 | 2007-10-23 2:33 | 2011-02-16 23:43 | MySQL Cluster: Disk Data | Closed (5517 days) | S3 | 5.1.22 | Any | Any | Select statement got warning after add a long name log/data file |
31782 | 2007-10-23 10:58 | 2011-02-16 23:43 | MySQL Cluster: Disk Data | Closed (5160 days) | S3 | mysql-5.1 | Linux | Any | No way to detect empty tablespaces using SQL |
41036 | 2008-11-25 22:23 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified | S4 | mysql-5.1-telco-7.0 | Any | Any | Easier Configuration Change On Cluster Disk Objects |
41274 | 2008-12-06 2:50 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified (5592 days) | S3 | mysql-5.1-telco-6.3 | Linux | Any | error 1504 'Out of logbuffer memory' message is too vague |
42480 | 2009-01-30 14:13 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified (5537 days) | S3 | mysql-5.1-telco-6.3 | Linux | Any | Low setting for SharedGlobalMemory gives erroneous error 707 msg |
43241 | 2009-02-26 17:54 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified | S3 | mysql-5.1-telco-6.3 | Any | Any | Inconsistancy in warnings on create table / create tablespace with unknown engin |
51111 | 2010-02-11 16:21 | 2011-02-16 23:44 | MySQL Cluster: Disk Data | Closed (5138 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | ALTER LOGFILE GROUP missing error message |
59502 | 2011-01-14 13:13 | 2011-02-16 23:44 | MySQL Cluster: Disk Data | Closed (4811 days) | S3 | Any | Any | race condition in drop logfile group | |
40999 | 2008-11-25 5:34 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified | S4 | mysql-5.1-telco-6.3 | Any | Any | Cluster cannot increase undo log buffer size. |
53106 | 2010-04-23 11:07 | 2011-03-07 13:01 | MySQL Cluster: Disk Data | Closed (4771 days) | S3 | mysql-5.1-telco-7.0 | Linux | Any | Weird behavior with undo_buffer_size to large for SharedGlobalMemory |
54199 | 2010-06-03 12:10 | 2011-02-16 23:44 | MySQL Cluster: Disk Data | Closed (4882 days) | S3 | mysql-5.1-telco-7.1 | Linux | Any | Cluster+DiskData, Querying INFORMATION_SCHEMA.FILES slow when data node is down |
18780 | 2006-04-04 19:47 | 2006-06-14 0:39 | MySQL Cluster: Disk Data | Closed (6498 days) | S1 | 5.1.9 | Linux (Linux) | Any | DD: DBT2 causes cluster failure using disk data in dbtup/DbtupDiskAlloc.cpp |
20053 | 2006-05-24 19:42 | 2006-07-03 16:53 | MySQL Cluster: Disk Data | Closed (6479 days) | S2 | 5.1.12 | Linux (Linux 32 Bit OS) | Any | TABLESPACE should only be allowed to drop files that are created for that TS |
22704 | 2006-09-26 17:06 | 2007-07-05 21:10 | MySQL Cluster: Disk Data | Can't repeat (6112 days) | S1 | 5.1.12-main | Linux (Linux 32 Bit OS) | Any | Cluster Crashes during NR while DD schema operations are being handled |
24631 | 2006-11-27 19:57 | 2007-05-23 15:50 | MySQL Cluster: Disk Data | Closed (6155 days) | S2 | 5.1.14-bk | Linux (Linux FC4) | Any | DD files aren't deleted when stopped node started again |
25117 | 2006-12-17 8:19 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified (6303 days) | S3 | mysql-5.1 | Linux (Linux FC4) | Any | mysql hangs if during creating logfile group or tablespace one ndbd was stopped |
27712 | 2007-04-09 10:02 | 2007-04-27 12:30 | MySQL Cluster: Disk Data | Closed (6181 days) | S3 | 5.1.18-bk | Linux (FC4 64bit) | Any | Single user mode. Creating logfile group and tablespace is allowed |
31333 | 2007-10-02 9:43 | 2008-05-19 6:25 | MySQL Cluster: Disk Data | Closed (5793 days) | S2 | 5.1.22 RC | Solaris (SunOS 5.11 snv_40) | Any | I can't create logfile group in MySQL 5.1.22 of SunOS. |
62858 | 2011-10-21 9:59 | 2014-04-07 9:05 | MySQL Cluster: Disk Data | Closed (3644 days) | S3 | 5.5.15-ndb-7.2.1 | Linux | Any | CREATE LOGFILE GROUP / CREATE TABLESPACE accept only bytes as unit |
21172 | 2006-07-20 3:47 | 2006-09-01 13:29 | MySQL Cluster: Disk Data | Closed (6419 days) | S2 | 5.1.11 | Linux (Debian Sarge 3.1) | Any | Cluster will not restart, configuration error |
24560 | 2006-11-23 21:48 | 2007-04-30 9:30 | MySQL Cluster: Disk Data | Closed (6178 days) | S2 | 5.1.14-bk | Linux (Linux FC4) | Any | UNDO_BUFFER_SIZE <= 64K in CREATE LOGFILE GROUP -> data node failure |
25428 | 2007-01-05 7:06 | 2012-05-18 20:19 | MySQL Cluster: Disk Data | Duplicate (6293 days) | S2 | MySQL 5.1.14 | Linux (RHEL 4) | Any | The Text column, not being indexed, although it is still stored in memory |
63822 | 2011-12-21 11:59 | 2012-01-09 10:38 | MySQL Cluster: Disk Data | Not a Bug (4463 days) | S1 | ndb-7.1.17 | Linux (RedHat EL6) | Any | Failed to create UNDOFILE |
74510 | 2014-10-22 14:09 | 2015-05-15 9:46 | MySQL Cluster: Disk Data | Closed (3241 days) | S1 | 7.1.33 | Any | Any | DICT master crash during takeover during \'rollforward\' of schemaTrans |
22020 | 2006-09-05 13:50 | 2013-10-06 20:45 | MySQL Cluster: Disk Data | Duplicate (6415 days) | S1 | 5.1 | Linux (Linux) | Any | ndb_dd_<various> tests fail, amd64 Linux |
16341 | 2006-01-10 14:23 | 2006-06-28 5:49 | MySQL Cluster: Disk Data | Closed (6484 days) | S3 | 5.1.5-alpha | Linux (Linux) | Any | DD: Failed CREATE LOGFILE GROUP/TABLESPACE should back out all changes |
19883 | 2006-05-17 13:58 | 2006-08-16 8:49 | MySQL Cluster: Disk Data | Can't repeat (6435 days) | S1 | 5.1 | Linux (Linux) | Any | ndbd seg fault with gcc 4.0.2 |
20052 | 2006-05-24 19:15 | 2012-05-18 20:19 | MySQL Cluster: Disk Data | Duplicate (6511 days) | S3 | 5.1.12 | Linux (Linux 32 Bit OS) | Any | Failure of CREATE TABLE SPACE should rollback TS name from cluster db |
22881 | 2006-10-02 8:43 | 2006-10-24 9:05 | MySQL Cluster: Disk Data | Not a Bug (6366 days) | S3 | 5.1.11 | Linux (ubuntu dapper drake linux) | Any | CREATE LOGFILE GROUP ADD UNDOFILE incompatible with local datanodes |
34102 | 2008-01-28 12:53 | 2011-02-16 23:43 | MySQL Cluster: Disk Data | Closed (5517 days) | S3 | 5.1.23 ndb 6.3.7; ndb 6.3.13 | Linux | Any | Creating LOGFILE group crashes cluster |
48089 | 2009-10-15 15:41 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | In progress (5133 days) | S3 | mysql-5.1-telco-7.0 | Any | Any | Can't change UNDO_BUFFER_SIZE with ALTER LOGFILE GROUP ... |
20839 | 2006-07-03 23:50 | 2006-12-06 9:09 | MySQL Cluster: Disk Data | Closed (6323 days) | S3 | 5.1 | Linux (Linux) | Any | Required tablespace and logfile group definitions not output by mysqldump |
21981 | 2006-09-03 9:31 | 2006-09-06 12:16 | MySQL Cluster: Disk Data | Closed (6414 days) | S3 | Any | ndbd crashes during CREATE LOGFILE GROUP if compiled with gcc4 (on some platform | ||
23733 | 2006-10-27 18:30 | 2007-02-02 8:51 | MySQL Cluster: Disk Data | Closed (6265 days) | S3 | 5.1.13 | Linux (Linux 32 Bit) | Any | INFORMATION_SCHEMA.FILES shows unknown null file after LOGFILE GROUP created |
25743 | 2007-01-21 18:03 | 2007-03-23 10:28 | MySQL Cluster: Disk Data | Closed (6216 days) | S2 | 5.1.15-bk | Linux (Linux FC4 64bit) | Any | If initial_size less than undo_buffer_size (for LG) then ndbd nodes are crashed |
26641 | 2007-02-26 16:57 | 2012-05-18 20:19 | MySQL Cluster: Disk Data | Duplicate (6113 days) | S2 | 5.1.14(beta) | Linux (Red Hat ES 4) | Any | Temporary error 1501 'Out of undo space' kills datanode |
29186 | 2007-06-18 22:36 | 2008-02-20 21:57 | MySQL Cluster: Disk Data | Closed (5882 days) | S1 | mysql-5.1 | Linux | Any | write >4gb into 1 datafile on a 32-bit computer, offset wraps causing corruption |
31133 | 2007-09-21 15:25 | 2007-10-15 9:56 | MySQL Cluster: Disk Data | Can't repeat (6010 days) | S3 | 5.1bk | Any | Any | Disk based statements not accepting magnitude suffixes |
31784 | 2007-10-23 11:18 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified | S3 | mysql-5.1 | Linux | Any | Tablespace and Logfile group operations not allowed within INFORMATION_SCHEMA |
33619 | 2008-01-02 9:19 | 2008-02-20 21:58 | MySQL Cluster: Disk Data | Closed (5882 days) | S1 | 5.1.22-rc community edition | Linux (2.6.9-8.11smp i386 GNU/Linux) | Any | Cluster Disk Data: sysbench causes ndbd crash using disk data |
34103 | 2008-01-28 12:58 | 2012-05-18 20:19 | MySQL Cluster: Disk Data | No Feedback (5768 days) | S3 | 5.1.23 ndb 6.3.7 | Linux | Any | create undo file outside datadir fails |
112193 | 2023-08-28 3:07 | 2023-10-10 11:02 | MySQL Cluster: plugin | Can't repeat (171 days) | S3 | 5.7 | Any | Any | All nodes elected as PRIMARY |
66914 | 2012-09-21 17:43 | 2018-08-17 10:32 | MySQL Cluster: Packaging | Closed (2051 days) | S3 | 7.2.8-1.el6 | Linux (Fedora 12) | Any | MySQL-Cluster-devel does not provide mysql-delel |
111978 | 2023-08-04 14:22 | 2023-08-10 14:27 | MySQL Cluster: Replication | Can't repeat (232 days) | S1 | 8.0.30 | CentOS (CentOS Linux release 7.7.1908 (Core)) | x86 (Intel(R) Xeon(R) Gold 5220 CPU @ 2.20GHz) | Our PRD env mysql 8.0.30 group-replication cluster lost some data |
2028 | 2003-12-05 22:45 | 2003-12-05 23:57 | MySQL Server: Compiling | Not a Bug (7420 days) | S2 | mysql-4.0.16 (Source distribution) | Linux (Linux first 2.4.19 i686) | Any | source compiles but does not run due to permissions problems |
27190 | 2007-03-15 21:30 | 2007-03-15 21:54 | MySQL Server: Compiling | Can't repeat (6224 days) | S2 | 5.0.37 | Linux (Linux (tar.gz download)) | Any | Information Schema test fails |
42900 | 2009-02-16 19:03 | 2009-02-16 19:33 | MySQL Server: Compiling | Not a Bug (5520 days) | S3 | 5.1.3.0 | Windows (XP) | Any | aggregate function and column name allowed in select list without group by |
11721 | 2005-07-04 12:45 | 2005-07-04 19:54 | MySQL Server: Compiling | Duplicate (6843 days) | S3 | 4.0.12 | Solaris (solaris 10 x86) | Any | MySQL 4.1.10 64 bit compiled code make test fail (Solaris 10 x86, Studio 10) |
84636 | 2017-01-24 12:05 | 2017-01-26 15:16 | MySQL Server: Compiling | Closed (2619 days) | S3 | 5.7.18 | Any | Any | group replication, broken one-definition rule |
87938 | 2017-10-02 8:53 | 2018-02-06 23:05 | MySQL Server: Compiling | Closed (2331 days) | S3 | 8.0.4 | Any | Any | Implement -DWITH_SSL=system for OsX and Windows |
96525 | 2019-08-13 21:56 | 2019-12-16 13:36 | MySQL Server: Compiling | Closed (1577 days) | S3 | 5.7 | Ubuntu | Any | Huge malloc when open file limit is high |
89688 | 2018-02-16 8:49 | 2018-06-09 6:49 | MySQL Server: Compiling | Verified (2120 days) | S4 | 5.7.21, 8.0.3, 8.0.4 | Any (linux and macos) | Any | server crash when group replication starts with mysqld-debug |
30732 | 2007-08-30 19:03 | 2007-09-30 19:09 | MySQL Server: Compiling | No Feedback (6025 days) | S2 | 5.0.32 | Windows (XP Professional) | Any | Really long query can't handle use of GROUP function |
96217 | 2019-07-16 9:25 | 2019-07-30 10:50 | MySQL Server: Connection Handling | Can't repeat (1704 days) | S3 | 8.0 | Any | Any | Confliction of resource group and thread pool plugin, invalid memory access |
109105 | 2022-11-16 3:17 | 2022-11-16 9:24 | MySQL Server: Connection Handling | Verified (499 days) | S4 | 8.0.28 | Linux | Any | Specify a default resource group for a user |
94283 | 2019-02-11 21:01 | 2020-06-04 12:42 | MySQL Server: Data Dictionary | Duplicate (1394 days) | S5 | 8.0.15 | Ubuntu | Any | MySQL 8.0.15 is slower than MySQL 5.7.25 |
103583 | 2021-05-05 8:21 | 2021-05-18 13:36 | MySQL Server: DDL | Closed (1046 days) | S1 | 8.0.24, 8.0.23, 8.0.21 | Any | Any | Dump/Restore fails with nested VIEWS having ROLLUP over DISTINCT groups |
112951 | 2023-11-03 10:05 | 2023-11-03 10:22 | MySQL Server: DDL | Verified (147 days) | S6 | 8.1.0, 8.0.35, 8.2.0 | Any | Any | Assertion `fixed' failed in MySQL 8.1.0 |
89018 | 2017-12-21 18:17 | 2019-05-19 14:10 | MySQL Server: DDL | Closed (1776 days) | S3 | 5.7.17, 5.7.20, 5.6.38 | Windows | Any | MySQL creates foreign key constraint when index in parent table is missing |
101740 | 2020-11-25 0:44 | 2020-12-08 15:14 | MySQL Server: DDL | Closed (1207 days) | S1 | 8.0.22 | Any | Any | mysqldump and SHOW CREATE VIEW produce invalid syntax for VIEWs with ROLL UP |
11640 | 2005-06-29 13:29 | 2008-10-03 20:22 | MySQL Server: DDL | Won't fix (5656 days) | S4 | Any | Any | automatic key creation on CREATE TABLE ... SELECT | |
31293 | 2007-09-29 16:57 | 2011-02-16 23:43 | MySQL Server: DDL | Closed (4916 days) | S3 | 5.1.22-ndb-6.3.2-telco-log | Any | Any | create logfile group/tablespace returns OK with warning when engine=myisam |
112470 | 2023-09-26 9:30 | 2023-09-26 9:34 | MySQL Server: DDL | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/item_sum.cc:642 |
111770 | 2023-07-17 2:59 | 2023-09-12 11:12 | MySQL Server: DDL | Verified (255 days) | S1 | 8.0.30, 8.0.33 | Any | Any | group replication lost transaction when import tablespace failed |
112516 | 2023-09-26 12:29 | 2023-09-26 12:33 | MySQL Server: DDL | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/item.cc:1202 |
49747 | 2009-12-16 20:03 | 2009-12-17 15:46 | MySQL Server: DDL | Not a Bug (5216 days) | S3 | 5.1.37 | Linux | Any | ERROR CREATE VIEW |
74585 | 2014-10-27 9:39 | 2015-12-22 6:07 | MySQL Server: DDL | Duplicate (3020 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6, 5.5.40 | Linux (CentOS 7) | Any | Failing assertion: *mbmaxlen < 5 in ha_innodb.cc line 1588 |
75851 | 2015-02-10 19:21 | 2015-08-04 9:43 | MySQL Server: DDL | Verified (3160 days) | S2 | 5.6.22, 5.6.25, 5.6.27 | Any | Any | SHOW CREATE VIEW should retain original view formatting and definition |
81377 | 2016-05-11 8:50 | 2017-01-27 15:52 | MySQL Server: DDL | Closed (2675 days) | S3 | 5.7 | Any | Any | Specifying a name for view's column in CREATE VIEW makes SELECT fail |
51318 | 2010-02-19 10:48 | 2011-02-16 23:44 | MySQL Server: DDL | Verified | S4 | 5.1 | Any | Any | implement "if exists" for DROP LOGFILE GROUP, DROP TABLESPACE commands |
40094 | 2008-10-16 22:59 | 2009-02-04 10:29 | MySQL Server: DDL | Not a Bug (5532 days) | S4 | 5.1 | Linux | Any | Allow group read/write/execute at filesystem on database create |
63996 | 2012-01-11 16:36 | 2012-01-12 12:42 | MySQL Server: DDL | Won't fix (4460 days) | S4 | 5.5.19 | Windows | Any | column_fuction(group_function)) error |
72589 | 2014-05-09 6:31 | 2019-11-24 5:16 | MySQL Server: DDL | Open (3612 days) | S4 | 5.6.17 | Windows (XP, 7 , 8) | Any | No relevant pivot table/crosstab sql query unlike Microsoft |
74487 | 2014-10-21 19:07 | 2015-02-16 20:38 | MySQL Server: DDL | Closed (3329 days) | S3 | 5.7.5-labs-preview | Any | Any | primary key missing for query_rewrite.rewrite_rules |
75484 | 2015-01-13 2:18 | 2015-01-19 18:35 | MySQL Server: DDL | Open (3357 days) | S4 | Any | Any | triggers - use NEW or OLD data as table references | |
60719 | 2011-04-01 8:40 | 2018-02-11 13:27 | MySQL Server: DML | Can't repeat (2238 days) | S3 | 5.5.10, 5.5.9 | Any | Any | Field info in EXPLAIN EXT./GROUP BY WITH ROLLUP says NOT NULL and contains NULL |
62097 | 2011-08-05 18:18 | 2011-08-05 19:32 | MySQL Server: DML | Duplicate (4620 days) | S1 | 5.5 | Windows (xp) | Any | unable to run a select statement |
62656 | 2011-10-07 18:07 | 2012-01-27 1:00 | MySQL Server: DML | No Feedback (4446 days) | S2 | 5.5.16 | Windows (sever 2003 32 bit) | Any | mysqldump losing connection on Big tables: Lost connection to MySQL server |
62755 | 2011-10-16 2:59 | 2011-11-23 12:51 | MySQL Server: DML | Duplicate (4510 days) | S3 | 5.5.16; 5.1.59 | Windows (XP SP3) | Any | Unexpect "ERROR 1062 (23000): Duplicate entry '...' for key 'group_key'" error |
68529 | 2013-02-28 20:43 | 2018-03-08 23:44 | MySQL Server: DML | Closed (2213 days) | S1 | 5.0/5.1/5.5 | Linux (gentoo/i686) | Any | GROUP_CONCAT(.... ORDER BY ...) prevents ORDER BY if using a VIEW |
70444 | 2013-09-26 21:57 | 2013-12-02 13:57 | MySQL Server: DML | Verified (3770 days) | S3 | 5.5.31 | Any | Any | MyISAM engine doesnt use index for count(distinct field) query |
73283 | 2014-07-13 18:22 | 2019-11-19 22:22 | MySQL Server: DML | Closed (1592 days) | S3 | 5.6.17, 5.6.20, 5.7.4 | Any | Any | FOUND_ROWS() returns 0 on SELECT COUNT(*) of impossible where |
73436 | 2014-07-30 13:55 | 2015-09-06 12:02 | MySQL Server: DML | Verified (3529 days) | S3 | 5.5.38, 5.6.19, 5.6.21 | Linux (debian-linux-gnu (x86_64)) | Any | format() with locale it_IT return wrong format |
74418 | 2014-10-16 10:17 | 2019-11-20 21:26 | MySQL Server: DML | Can't repeat (1591 days) | S6 | 5.6.20, 5.6.22, 5.6.35 | Any | Any | Item_in_subselect::val_int(): Assertion `0' failed. in sql/item_subselect.cc:136 |
74447 | 2014-10-20 9:04 | 2018-10-01 16:17 | MySQL Server: DML | Closed (3431 days) | S6 | 5.6.20, 5.6.22, 5.7.6 | Any | Any | Assertion `n < m_size' failed. | abort in Bounds_checked_array |
74448 | 2014-10-20 9:18 | 2014-10-24 8:10 | MySQL Server: DML | Verified (3448 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion `table_share->tmp_table != NO_TMP_TABLE || m_lock_type != 2' failed |
74500 | 2014-10-22 9:56 | 2017-08-16 13:23 | MySQL Server: DML | Closed (3420 days) | S3 | 5.6.20-debug | Linux (CentOS 7) | Any | Assertion `src' failed in my_strnxfrm_unicode (sig 6 -strings/ctype-utf8.c:5151) |
74537 | 2014-10-24 6:53 | 2014-10-24 11:19 | MySQL Server: DML | Verified (3444 days) | S3 | 5.6.20-debug, 5.6.22 | Linux (CentOS 7) | Any | Assertion `lex.sphead == __null' failed in Table_triggers_list::check_n_load |
74705 | 2014-11-06 2:53 | 2014-11-06 3:16 | MySQL Server: DML | Not a Bug (3431 days) | S3 | 5.6.17-log | Any | Any | The having results are not accurate |
74747 | 2014-11-08 7:20 | 2015-02-05 7:55 | MySQL Server: DML | Verified (3340 days) | S1 | 5.6.20, 5.6.22, 5.7.5 | Any | Any | Failing assertion: index->id == btr_page_get_index_id(page) btr0cur.cc line 899 |
74777 | 2014-11-11 6:14 | 2019-11-20 21:58 | MySQL Server: DML | Can't repeat (1591 days) | S3 | 5.6.21-debug, 5.6.23, 5.7.6 | Any | Any | Assertion :bitmap_is_subset(&m_part_info->lock_partitions, &m_locked_partitions) |
74779 | 2014-11-11 7:42 | 2016-07-29 10:37 | MySQL Server: DML | Verified (3426 days) | S3 | 5.6.20-debug, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | Assertion :bitmap_is_s et(&m_part_info->read_partitions, m_part_spec.start_part) |
74780 | 2014-11-11 9:15 | 2016-11-18 6:33 | MySQL Server: DML | Verified (3426 days) | S3 | 5.6.20-debug, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | Assertion `tab->ref.use_count' failed in join_read_key_unlock_row |
74877 | 2014-11-15 17:00 | 2018-10-01 16:17 | MySQL Server: DML | Verified (2671 days) | S6 | 5.6.21 | Linux (CentOS 7) | Any | Assertion `false' failed in JOIN::decide_subquery_strategy |
74889 | 2014-11-17 5:20 | 2019-11-25 21:39 | MySQL Server: DML | Can't repeat (1586 days) | S3 | 5.6.21 | Linux (CentOS 7) | Any | Sig-6 abort in Item_in_subselect::exec | sql/item_subselect.cc:730 |
74946 | 2014-11-21 4:47 | 2014-11-23 9:19 | MySQL Server: DML | Verified (3416 days) | S3 | 5.6.20, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | Assertion `nr >= 0.0' failed in virtual double Item_sum_std::val_real() |
75648 | 2015-01-27 10:04 | 2015-01-27 11:12 | MySQL Server: DML | Verified (3349 days) | S3 | 5.6.21-debug, 5.6.24, 5.7.6 | Linux (CentOS 7) | Any | Assertion `length <= max_data_length()' failed in Field_blob::store_to_mem |
76244 | 2015-03-10 16:31 | 2018-07-26 1:00 | MySQL Server: DML | No Feedback (2074 days) | S2 | 5.6.18, 5.1.73+ | Any | Any | MySQL does order of operations incorrectly on distinct numeric string |
76430 | 2015-03-22 22:26 | 2018-09-25 22:04 | MySQL Server: DML | Closed (3285 days) | S6 | 5.7.6-m16, 5.7.6, 5.7.8, 8.0.0 | Any | Any | InnoDB: Failing assertion: (&dict_sys->mutex)->is_owned() | file dict0priv.ic 44 |
76925 | 2015-05-04 10:37 | 2015-05-04 11:20 | MySQL Server: DML | Verified (3252 days) | S3 | 5.6.23, 5.6.25 | Linux (CentOS 7) | Any | handle_fatal_signal (sig=11) in ha_innobase::store_key_val_for_row |
77580 | 2015-07-01 11:45 | 2015-07-02 16:14 | MySQL Server: DML | Closed (3193 days) | S3 | 5.6.23, 5.6.27 | CentOS (CentOS 7) | Any | Assertion `t1->result_range' failed in sql/gcalc_tools.cc:731 |
77874 | 2015-07-29 15:41 | 2018-03-06 17:13 | MySQL Server: DML | Not a Bug (2215 days) | S3 | 5.5.28-0 | Ubuntu (Ubuntu 0.12.04.2) | Any | ORDER BY MAX() Returns a row with empty value when no rows exist |
78292 | 2015-08-31 16:48 | 2015-11-13 13:48 | MySQL Server: DML | Closed (3059 days) | S3 | 5.6.22 | CentOS (CentOS 7) | Any | Assertion `pfs->m_processlist_id != 0' failed in table_session_connect.cc:254 |
78361 | 2015-09-08 7:08 | 2015-10-24 18:08 | MySQL Server: DML | Closed (3079 days) | S3 | 5.6.22, 5.6.26 | Any | Any | Column alias can be used in subquery in select list in the same query |
79527 | 2015-12-04 12:58 | 2017-08-08 19:08 | MySQL Server: DML | Verified (2425 days) | S3 | 5.6.27 | Any | Any | Errorcode 175: abort in group by on big tables |
79567 | 2015-12-09 7:41 | 2019-11-28 22:55 | MySQL Server: DML | Closed (1583 days) | S3 | 5.7.8, 5.5.48, 5.6.29, 5.7.9 | Any | Any | Output scale for IFNULL() with join is not correct |
80440 | 2016-02-19 6:13 | 2016-02-19 9:12 | MySQL Server: DML | Duplicate (2961 days) | S3 | 5.6.29, 5.6.30 | CentOS | Any | Assertion `item_in->left_expr->cols() == 1' failed in sql/item_subselect.cc:382 |
80759 | 2016-03-16 8:27 | 2019-12-11 22:24 | MySQL Server: DML | Closed (1570 days) | S6 | 5.6.29, 5.7.11, 5.5.48 | CentOS | Any | Assertion `table_ref->has_record in join_read_key(JOIN_TAB*) |
112500 | 2023-09-26 11:41 | 2023-09-26 11:50 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/item_sum.cc:4127 |
112475 | 2023-09-26 9:43 | 2023-09-26 9:46 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_select.cc:2303 |
111585 | 2023-06-27 15:18 | 2023-06-28 18:28 | MySQL Server: DML | Closed (275 days) | S6 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | Order by aggregate assertion error |
112479 | 2023-09-26 10:29 | 2023-09-26 14:13 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_executor.cc:4222 |
112480 | 2023-09-26 10:31 | 2023-09-26 14:07 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/handler.cc:2966 |
112487 | 2023-09-26 11:01 | 2023-09-26 11:41 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_optimizer.cc:343 |
112491 | 2023-09-26 11:14 | 2023-09-27 15:41 | MySQL Server: DML | Closed (184 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/item_subselect.cc:2415 |
112497 | 2023-09-26 11:32 | 2023-09-26 11:46 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/field.cc:7108 |
112501 | 2023-09-26 11:44 | 2023-09-26 11:50 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/item_sum.cc:784 |
112503 | 2023-09-26 11:48 | 2023-12-20 19:54 | MySQL Server: DML | Closed (100 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/field.cc:7119 |
112513 | 2023-09-26 12:22 | 2023-09-26 12:27 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/item.h:2103 |
112517 | 2023-09-26 12:32 | 2023-09-26 12:36 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/item.cc:8044 |
112518 | 2023-09-26 12:33 | 2023-09-26 12:39 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/item_func.cc:1881 |
112521 | 2023-09-26 12:40 | 2023-09-26 13:06 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Abort in /mysql-8.0.34/sql/signal_handler.cc:286 |
113385 | 2023-12-09 11:48 | 2024-03-11 11:00 | MySQL Server: DML | Closed (21 days) | S6 | 8.2 | Any | Any | Intersect decimal precision assertion error |
81302 | 2016-05-04 6:41 | 2023-04-09 11:55 | MySQL Server: DML | Verified (2886 days) | S3 | 5.7.8, 5.6.30, 5.7.12 | Any | Any | w/o group by, query with column in having clause not in select list, succeeds |
81408 | 2016-05-13 3:14 | 2020-01-31 13:32 | MySQL Server: DML | Closed (1519 days) | S6 | 5.5.49, 5.6.30 | Any | Any | void Item_row::illegal_method_call(const char*): Assertion `0' failed. |
81410 | 2016-05-13 4:12 | 2019-01-23 11:50 | MySQL Server: DML | Unsupported (1892 days) | S1 | 5.5.49 | Any | Any | Assertion `multi_range_length > 0' failed. in QUICK_RANGE_SELECT::reset |
81413 | 2016-05-13 4:54 | 2019-12-16 22:29 | MySQL Server: DML | Closed (1565 days) | S6 | 5.5.49 | Any | Any | Assertion `is_last_prefix <= 0' failed. |
81532 | 2016-05-23 2:01 | 2019-12-16 22:40 | MySQL Server: DML | Closed (1565 days) | S6 | 5.6.30 | Any | Any | virtual enum_field_types Item::field_type() const: Assertion `0' failed. |
82616 | 2016-08-17 14:57 | 2016-08-18 10:04 | MySQL Server: DML | Duplicate (2780 days) | S4 | 5.6 | Any | Any | implement LIMIT N in GROUP_CONCAT |
83021 | 2016-09-16 10:02 | 2016-09-16 10:16 | MySQL Server: DML | Verified (2751 days) | S3 | 5.6.33, 5.5.52 | Any | Any | Assertion "buf != end" failed |
83162 | 2016-09-27 8:01 | 2016-09-27 11:11 | MySQL Server: DML | Duplicate (2740 days) | S3 | 5.7, 5.7.15 | Linux | Any | ordered result should have been returned |
83699 | 2016-11-04 21:18 | 2017-10-20 18:24 | MySQL Server: DML | Closed (2359 days) | S3 | 5.8 | Any | Any | Wrong calculation of decimals after point for IFNULL w/ GROUP BY using tmp tbl |
84076 | 2016-12-06 10:06 | 2018-10-01 16:17 | MySQL Server: DML | Verified (2670 days) | S6 | 5.6.34 | Any | Any | Assertion `thd->is_error() || kill_errno' failed. |
84445 | 2017-01-09 9:29 | 2021-03-12 5:37 | MySQL Server: DML | Duplicate (2012 days) | S1 | 5.7.16, 5.7.17 | Linux | Any | select distinct with constant value for left join mysql 5.7.16 |
88133 | 2017-10-18 6:42 | 2017-11-07 14:04 | MySQL Server: DML | Duplicate (2334 days) | S3 | 5.6.37 | Any | Any | Conditional jump or move depends on uninitialised value (gcalc_tools.cc:1276) |
88805 | 2017-12-07 8:40 | 2017-12-07 9:37 | MySQL Server: DML | Verified (2304 days) | S1 | 5.6.38 | Any | Any | Assertion `item_in->left_expr->cols() == 1' failed. |
89094 | 2018-01-02 14:06 | 2018-01-03 8:07 | MySQL Server: DML | Can't repeat (2277 days) | S2 | 5.7.19 | Debian | Any | Data inconsistency on master after upgrading to 5.7.19 |
89101 | 2018-01-04 1:52 | 2020-03-30 12:12 | MySQL Server: DML | Verified (2262 days) | S2 | 5.7.20 | Any | Any | MySQL server hang when gtid_mode=on and innodb_thread_concurrency>0 |
90803 | 2018-05-09 9:24 | 2018-12-05 4:59 | MySQL Server: DML | Closed (2139 days) | S3 | 8.0.11 Community Server | Any | Any | regexp_replace accumulating result |
92898 | 2018-10-23 13:08 | 2018-10-23 19:37 | MySQL Server: DML | Not a Bug (1984 days) | S2 | 8.0.13 | Linux (Slackware64 current) | x86 | Error MY-013235 Error in parsing View during upgrade with MySQL 8.0.13 |
99005 | 2020-03-20 11:31 | 2020-03-20 12:17 | MySQL Server: DML | Verified (1470 days) | S2 | 5.6/5.7/8.0 | Any | Any | Flags of column-type-info is different |
100164 | 2020-07-09 1:45 | 2020-07-09 13:19 | MySQL Server: DML | Not a Bug (1359 days) | S3 | 8.0.20 | Any | Any | resolve problem in group by and order by field with 2 tables in 2 schema |
101166 | 2020-10-14 11:56 | 2020-11-15 1:00 | MySQL Server: DML | No Feedback (1231 days) | S3 | 8.0.13 | CentOS | Any | regexp_substr |
101175 | 2020-10-14 18:12 | 2021-02-17 11:11 | MySQL Server: DML | Closed (1136 days) | S3 | 8.0.21 | Ubuntu (Ver 8.0.21-0ubuntu0.20.04.4) | Any | COALESCE and IFNULL do not work as expected in WITH ROLLUP queries |
101304 | 2020-10-24 4:58 | 2020-10-24 14:19 | MySQL Server: DML | Verified (1252 days) | S2 | 5.7 thru 8.0.21 | Debian (Buster) | x86 (KVM VM) | mysql 5.7, 8 insert on duplicate key update on view inserts nothing without err |
104411 | 2021-07-25 13:35 | 2021-08-13 15:23 | MySQL Server: DML | Closed (959 days) | S2 | 8.0.26 | MacOS (Mac OS X 10.14) | x86 | No result set returned when using HAVING COUNT(DISTINCT ...) |
106193 | 2022-01-18 6:43 | 2022-01-19 8:10 | MySQL Server: DML | Duplicate (800 days) | S2 | 8.0.27 | Windows | x86 | insert into select,coalesce(sum(),0) not work correct |
106539 | 2022-02-22 17:56 | 2022-03-07 9:56 | MySQL Server: DML | Not a Bug (753 days) | S3 | 8.0.28 | Any | Any | Wrong result for aggregate function. |
34620 | 2008-02-16 17:16 | 2008-03-15 8:41 | MySQL Server: DML | Closed (5858 days) | S3 | 5.0+, 5.0.58-BK | Any | Any | item_row.cc:50: Item_row::illegal_method_call(const char*): Assertion `0' failed |
74859 | 2014-11-14 9:50 | 2018-10-01 16:17 | MySQL Server: DML | Closed (3343 days) | S6 | 5.6.20, 5.6.23, 5.7.6 | Any | Any | Assertion `scale >= 0 && precision > 0 && scale <= precision' failed |
80186 | 2016-01-28 13:15 | 2016-01-28 13:54 | MySQL Server: DML | Not a Bug (2983 days) | S3 | 5.5.38-log | Windows | Any | the group by colunm is trimed when do group by |
80682 | 2016-03-10 8:44 | 2016-03-10 11:50 | MySQL Server: DML | Verified (2941 days) | S3 | 5.7.8, 5.7.11 | Any | Any | Inconsistent behavior with GROUP BY alias, w/ different sequence in select list |
99931 | 2020-06-18 19:41 | 2020-06-19 6:56 | MySQL Server: DML | Closed (1379 days) | S2 | 8.0.12, 8.0.18 | Any | Any | Aggregate group by returns incorrect result when loose index scan is used |
100734 | 2020-09-03 17:19 | 2020-10-04 1:00 | MySQL Server: DML | No Feedback (1273 days) | S3 | 8.021 | Any (Tried on windows, mac, centos) | x86 | Select with group by returns different results |
103930 | 2021-06-07 18:06 | 2021-06-08 13:55 | MySQL Server: DML | Verified (1025 days) | S2 | 5.7.34 | Any | Any | Result mismatch when unicode collation with special data |
112499 | 2023-09-26 11:37 | 2023-09-26 11:48 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_tmp_table.cc:485 |
112514 | 2023-09-26 12:23 | 2023-09-26 12:28 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_lex.cc:2288 |
112982 | 2023-11-07 8:08 | 2023-11-14 19:46 | MySQL Server: DML | Closed (136 days) | S6 | 8.0.34, 8.0.35 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_derived.cc:558 |
20344 | 2006-06-08 15:46 | 2019-10-29 21:03 | MySQL Server: DML | Closed (1613 days) | S4 | 5.0.21-max | MacOS (OS X) | Any | Order BY requires column presence in SELECT |
87577 | 2017-08-29 10:23 | 2017-08-29 10:25 | MySQL Server: DML | Duplicate (2404 days) | S1 | 5.7.19 | Any | Any | Field* Item::tmp_table_field_from_field_type(TABLE*, bool):Assertion `0' failed |
90245 | 2018-03-28 15:23 | 2018-03-29 2:43 | MySQL Server: DML | Verified (2192 days) | S3 | 5.7/8.0 | MacOS (10.13.3) | x86 | Wrong result when using GROUP BY and const value in a subquery |
90599 | 2018-04-24 9:41 | 2018-11-09 12:01 | MySQL Server: DML | Not a Bug (1967 days) | S3 | 8.0.11 | Any | Any | Window function with RAND() is not random with GROUP BY |
90792 | 2018-05-08 3:46 | 2018-05-09 20:28 | MySQL Server: DML | Verified (2152 days) | S3 | 5.7 | Fedora | x86 | ONLY_FULL_GROUP_BY CONCAT and FUNCTIONS |
92483 | 2018-09-18 14:06 | 2018-11-01 1:00 | MySQL Server: DML | No Feedback (1977 days) | S2 | 8.0.12 | Windows (10) | x86 | SELECT MAX GROUP BY failing with WHERE clause |
94206 | 2019-02-05 14:12 | 2019-02-06 8:23 | MySQL Server: DML | Verified (1879 days) | S2 | 5.7/8.0 | Ubuntu (5.7.25-0ubuntu0.18.04.2) | Any | IFNULL expression leaks out of outer join when using "distinct" or "group by" |
98663 | 2020-02-19 10:53 | 2020-04-02 12:22 | MySQL Server: DML | Closed (1458 days) | S3 | 8.0.16 | Any | Any | ROLLUP output is not reasonable when same fields exist in the group by syntax |
99587 | 2020-05-15 11:38 | 2020-05-18 12:35 | MySQL Server: DML | Duplicate (1411 days) | S2 | 8.0.20 | Debian | x86 | Invalid data returned when using LEFT OUTER JOIN and GROUP BY |
99846 | 2020-06-11 8:50 | 2020-06-11 10:45 | MySQL Server: DML | Closed (1387 days) | S3 | 8.0.20 | Debian | x86 | Non-deterministic query using GROUP BY |
100094 | 2020-07-02 21:25 | 2020-07-03 17:00 | MySQL Server: DML | Not a Bug (1365 days) | S3 | Ubuntu | Any | Referencing a column in HAVING clause yields to an error | |
100268 | 2020-07-20 17:13 | 2020-07-20 18:13 | MySQL Server: DML | Not a Bug (1348 days) | S2 | 8.0.20 | Any | Any | 8.0.20: LEFT JOIN w/ unique index does not work properly w/ non-strict GROUP BY |
102169 | 2021-01-07 9:42 | 2021-01-07 10:07 | MySQL Server: DML | Verified (1177 days) | S2 | 8.0.18, 5.6.50, 5.7.32, 8.0.22 | Any | Any | tinyint DIV a small value expression return wrong |
103194 | 2021-04-02 8:02 | 2021-04-02 15:32 | MySQL Server: DML | Not a Bug (1092 days) | S2 | 8.0.23 | Any | Any | Prepare execution result is wrong |
112293 | 2023-09-07 14:04 | 2023-09-08 6:54 | MySQL Server: DML | Verified (203 days) | S3 | 8.0, 8.0.34, 5.7.43 | Any | Any | Wrong result if non-breaking space is contained in varchar |
112319 | 2023-09-12 7:59 | 2023-09-13 8:50 | MySQL Server: DML | Closed (198 days) | S2 | 8.0.33, 8.0.34, 8.1.0 | Ubuntu | Any | GROUP_CONCAT with GROUP BY and WHERE clause turns NULL into empty strings. |
112462 | 2023-09-26 8:58 | 2023-09-26 9:05 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in home/wx/mysql-8.0.34/sql/sql_derived.cc:1641 |
112478 | 2023-09-26 10:24 | 2024-02-28 16:31 | MySQL Server: DML | Closed (30 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_derived.cc:524 |
112495 | 2023-09-26 11:26 | 2023-09-26 11:46 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_optimizer.cc:8930 |
112983 | 2023-11-07 8:11 | 2023-11-08 5:25 | MySQL Server: DML | Verified (143 days) | S6 | 8.0.34, 8.0.35 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_base.cc:7731 |
113037 | 2023-11-10 7:00 | 2023-11-10 9:04 | MySQL Server: DML | Verified (140 days) | S6 | 8.0.34, 8.0.35, 8.1.0, 8.2.0 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/my_decimal.h:186 |
114186 | 2024-03-01 15:32 | 2024-03-01 16:02 | MySQL Server: DML | Verified (28 days) | S4 | 8.0 | Any | Any | Make ANY_VALUE standard compliant |
114282 | 2024-03-08 13:10 | 2024-03-08 13:13 | MySQL Server: DML | Verified (21 days) | S2 | 8.35, 8.0.36 | Any | Any | Inconsistent result may caused by group by NULL |
114312 | 2024-03-12 6:30 | 2024-03-19 2:26 | MySQL Server: DML | Verified (10 days) | S3 | 8.0 | Any | Any | Item_ref::used_tables wrong when ref to a rollup constant |
15426 | 2005-12-02 9:34 | 2011-06-25 0:41 | MySQL Server: DML | Won't fix (4661 days) | S4 | 4.1,5.0 | Linux (Linux) | Any | SQL_CALC_FOUND_ROWS |
24083 | 2006-11-08 11:02 | 2020-05-03 20:45 | MySQL Server: DML | Verified (5657 days) | S4 | 5.0.29-BK, 5.0.26-community | Linux (Linux, WinXP) | Any | GROUP BY expressions should be allowed in the HAVING clause |
31281 | 2007-09-28 15:09 | 2007-10-28 15:24 | MySQL Server: DML | No Feedback (5997 days) | S1 | 5.0.41-community-nt-log | Windows | Any | Group by and subquery issue in 5.0.41-community-nt-log |
34874 | 2008-02-27 9:47 | 2018-02-08 22:50 | MySQL Server: DML | Closed (2241 days) | S3 | 5.0+ | Any | Any | Wrong result with IN(SELECT aggregate FROM DUAL) |
14545 | 2005-11-01 17:01 | 2018-11-16 21:30 | MySQL Server: DML | Verified (6723 days) | S4 | Any (any) | Any | Median SQL Aggregate function | |
19173 | 2006-04-18 18:19 | 2011-02-16 23:43 | MySQL Server: DML | Verified (6243 days) | S4 | 5.0.20 | Linux (Linux) | Any | Foreign Key reference integrity |
40761 | 2008-11-15 19:17 | 2011-02-16 23:43 | MySQL Server: DML | Closed (5539 days) | S2 | 5.1.29/5.0/5.1/6.0 | Windows (WinXP (Intel-32)/Linux) | Any | LEFT JOIN on inline view crashes server |
44090 | 2009-04-04 18:44 | 2012-05-24 13:44 | MySQL Server: DML | Can't repeat (4327 days) | S3 | 5.0, 5.1, 6.0 bzr | Any | Any | ONLY_FULL_GROUP_BY sql_mode allows mixing of group columns with wild cards |
44399 | 2009-04-22 3:40 | 2011-02-16 23:43 | MySQL Server: DML | Closed (5390 days) | S2 | 5.1.34-community, 5.1.35-bzr | Windows (Windows XP SP3) | Any | crash with statement using TEXT columns, aggregates, GROUP BY, and HAVING |
44562 | 2009-04-29 21:41 | 2009-04-30 9:44 | MySQL Server: DML | Not a Bug (5447 days) | S2 | 5.1.30 | Windows (Vista) | Any | Multiple join, duplicate result |
45270 | 2009-06-02 17:08 | 2018-09-09 20:45 | MySQL Server: DML | Verified (5373 days) | S4 | 5.1 | Any | Any | Replacement for Groupwise-Max |
46176 | 2009-07-14 15:42 | 2011-02-16 23:44 | MySQL Server: DML | Closed (5372 days) | S4 | Any | Any | Aggregate function for strings (Concatenation) | |
47713 | 2009-09-29 12:51 | 2018-09-09 20:45 | MySQL Server: DML | Verified (5295 days) | S1 | 5.0.83, 5.1.39 | Any | Any | SELECT WITH ROLLUP returned wrong data when using CONCAT |
48421 | 2009-10-29 19:38 | 2018-02-11 11:03 | MySQL Server: DML | Can't repeat (2238 days) | S2 | 5.1 | Windows | Any | Failure of executing insert into table select ... from .... group by .. |
48985 | 2009-11-23 11:23 | 2011-02-16 23:44 | MySQL Server: DML | Closed (5131 days) | S1 | 5.1.40, 5.1.41 | Any | Any | show create table crashes if previous access to the table was killed |
49958 | 2009-12-28 13:48 | 2018-02-11 11:09 | MySQL Server: DML | Can't repeat (2238 days) | S1 | Any | Any | How Solve this Error - Errcode: 13 | |
62053 | 2011-08-02 4:14 | 2011-08-02 4:22 | MySQL Server: DML | Not a Bug (4623 days) | S1 | 5.5 | Any | Any | columns in SELECT clause not affected by group fn must be declared in GROUP BY |
78183 | 2015-08-24 9:01 | 2015-09-01 8:37 | MySQL Server: DML | Not a Bug (3132 days) | S3 | 5.6.22 | Any | Any | Similar query with aggregate functions returns inconsistent result |
78534 | 2015-09-23 17:29 | 2015-09-23 20:44 | MySQL Server: DML | Can't repeat (3110 days) | S3 | Any | Any | Different results are coming when ran a same Query in two different applications | |
55188 | 2010-07-12 21:01 | 2011-02-16 23:44 | MySQL Server: DML | Closed (4914 days) | S2 | 5.1.46sp1 | Any | Any | GROUP BY, GROUP_CONCAT and TEXT - inconsistent results |
62372 | 2011-09-07 11:48 | 2018-02-11 14:17 | MySQL Server: DML | Closed (2238 days) | S3 | 5.5.15, 5.5.17 | Any | Any | Wrong query results with SQL_CALC_FOUND_ROWS, GROUP BY, LIMIT and Using index |
34751 | 2008-02-21 22:19 | 2018-02-08 22:42 | MySQL Server: DML | Closed (2241 days) | S3 | 5.0+ | Any | Any | Inside HAVING clause subqueries with aggregates and without GROUP BY rise error |
78349 | 2015-09-06 12:12 | 2015-12-03 14:22 | MySQL Server: DML | Closed (3039 days) | S3 | 5.6.22, 5.6.26 | Any | Any | w/ ONLY_FULL_GROUP_BY, having/order by + column alias have different results |
78424 | 2015-09-14 2:29 | 2015-09-14 10:50 | MySQL Server: DML | Can't repeat (3119 days) | S3 | 5.7.7 | Any | Any | w/ c1&&c2 appears in select list, group by clause and order by clause, SQL fails |
99592 | 2020-05-15 15:23 | 2020-05-18 4:37 | MySQL Server: DML | Duplicate (1411 days) | S3 | 8.0.20 | Ubuntu | Any | GROUP BY includes wrong data |
100107 | 2020-07-03 16:57 | 2021-03-16 18:03 | MySQL Server: DML | Closed (1353 days) | S3 | 8.0.20 | MacOS | Any | MySQL 8.0.20 Bug? Groups duplicated when using GROUP BY and COUNT(DISTINCT ) |
30039 | 2007-07-25 13:35 | 2011-02-16 23:43 | MySQL Server: DML | Verified (6092 days) | S4 | Any | Any | Add "Using group-by" to Extra column in EXPLAIN output | |
65798 | 2012-07-03 15:16 | 2012-11-14 20:54 | MySQL Server: DML | Closed (4153 days) | S3 | 5.5.26 | Any | Any | ONLY_FULL_GROUP_BY documentation doesn't mention implicit group by |
67821 | 2012-12-05 22:37 | 2013-01-07 1:00 | MySQL Server: DML | No Feedback (4100 days) | S3 | 5.5.28 | Windows (7 Ultimate 64bit) | Any | GROUP BY not working in stored procedure |
74646 | 2014-10-31 9:51 | 2014-10-31 10:27 | MySQL Server: DML | Verified (3437 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion `((Item_result_field*)item)->result_field' failed in create_tmp_field |
74695 | 2014-11-05 5:25 | 2017-08-14 1:50 | MySQL Server: DML | Closed (3225 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Asser tion `args[0]->fixed' failed | sig 6 abort in sql/item_strfunc.h:882 |
32482 | 2007-11-18 17:45 | 2008-01-14 19:09 | MySQL Server: DML | Closed (5919 days) | S2 | 5.1.22-rc-log | Linux | Any | crash with GROUP BY alias_of_user_variable WITH ROLLUP |
35002 | 2008-03-03 14:17 | 2018-09-09 20:45 | MySQL Server: DML | Verified (5869 days) | S2 | 5.1.23-rc/5.1BK/5.0/6.0 | Linux (2.6.22.9-61.fc6) | Any | Wrong results returned when using derived table and group by |
39169 | 2008-09-01 22:17 | 2008-10-10 8:06 | MySQL Server: DML | No Feedback (5649 days) | S1 | 6.0.4alpha, 6.0.6alpha | Windows (Windows XP Home) | Any | Unexpected behaviour when using GROUP BY and/or WHERE clauses |
43912 | 2009-03-27 13:56 | 2012-10-16 5:00 | MySQL Server: DML | Won't fix (4182 days) | S3 | 5.0.91 | Any | Any | 'Column * cannot be null' when derived table has count() with no results |
45386 | 2009-06-09 3:52 | 2011-02-16 23:44 | MySQL Server: DML | Closed (5295 days) | S3 | 5.0.81, 5.0, 5.1, 6.0 bzr | Solaris | Any | Wrong query result with MIN function in field list, WHERE and GROUP BY clause |
45963 | 2009-07-06 8:48 | 2009-07-06 10:41 | MySQL Server: DML | Not a Bug (5380 days) | S4 | 5.0.75-0ubuntu10.2 (Ubuntu) | Any | Any | DWIM: Allow group functions in WHERE clause, by doing GROUP BY first |
47650 | 2009-09-25 16:53 | 2011-02-16 23:44 | MySQL Server: DML | Closed (5131 days) | S3 | 5.0.X, 5.1.39, next-mr | Any (Mac OS X Snow leopard, Linux) | Any | using group by with rollup without indexes returns incorrect results with where |
61943 | 2011-07-21 13:16 | 2012-07-11 9:38 | MySQL Server: DML | Verified (4283 days) | S4 | 5.5.12 | Any | Any | Syntax to specify a field from select_expr for Group By |
69470 | 2013-06-14 9:33 | 2013-06-14 13:08 | MySQL Server: DML | Duplicate (3941 days) | S3 | 5.6.10 | Linux | Any | Use "group by", but no aggregate function, get weird result |
69590 | 2013-06-26 15:59 | 2018-03-14 20:53 | MySQL Server: DML | Closed (2207 days) | S3 | 5.5.32 | Any | Any | Problem using between with group by functions |
69684 | 2013-07-07 10:44 | 2014-06-02 14:33 | MySQL Server: DML | Closed (3601 days) | S2 | 5.5, 5.6 | Any | Any | The update and select behave differently under the same conditions. |
74505 | 2014-10-22 12:22 | 2019-11-20 21:46 | MySQL Server: DML | Can't repeat (1591 days) | S3 | 5.6.20-debug | Linux (CentOS 7) | Any | Assertion tab->select->quick->index==(uint)best_key' in test_if_skip_sort_order |
88749 | 2017-12-05 2:41 | 2018-09-25 22:07 | MySQL Server: DML | Verified (2306 days) | S6 | 5.5.58 | Any | Any | Assertion `item->type() == Item::FIELD_ITEM || (item->type() == Item::REF_ITEM & |
99481 | 2020-05-08 6:30 | 2020-05-08 10:15 | MySQL Server: DML | Can't repeat (1421 days) | S3 | 5.7 | Windows | Any | Query with group by and sum works 99% of the times but fails occasionally |
101228 | 2020-10-19 15:55 | 2020-11-03 23:40 | MySQL Server: DML | Not a Bug (1242 days) | S2 | 8.0.22 | Any | Any | date group and sort groups similar dates in different groups |
102524 | 2021-02-08 9:07 | 2021-02-08 14:07 | MySQL Server: DML | Not a Bug (1145 days) | S2 | 8.0.18 | CentOS | Any | Wrong result when order by a function expression. |
109548 | 2023-01-09 7:55 | 2023-12-20 12:33 | MySQL Server: DML | Closed (100 days) | S5 | 8.0.13,8.0.31 | Any | Any | Poor performance when using HASH field to check unique |
110011 | 2023-02-09 15:20 | 2023-02-13 13:40 | MySQL Server: DML | Not a Bug (410 days) | S3 | 8.0.32 | Windows | Any | inconsistent behavior with group by and order by |
111441 | 2023-06-15 18:53 | 2023-06-22 17:57 | MySQL Server: DML | Closed (281 days) | S6 | 8.0.33 | Ubuntu (20.04 LTS) | x86 (Intel(R) Core(TM) i7-10700 CPU) | bool Sql_cmd_dml::prepare(THD*): Assertion `thd->is_error()' failed. |
112356 | 2023-09-15 10:13 | 2023-10-20 1:00 | MySQL Server: DML | No Feedback (162 days) | S2 | 8.0.25 | Linux | Any | SQL returns unexpected results |
112498 | 2023-09-26 11:35 | 2024-01-03 17:34 | MySQL Server: DML | Closed (86 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_resolver.cc:183 |
112502 | 2023-09-26 11:46 | 2023-09-26 11:49 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/item_sum.cc:1598 |
112512 | 2023-09-26 12:19 | 2023-09-26 12:23 | MySQL Server: DML | Verified (185 days) | S6 | 8.0.34 | Ubuntu (20.04) | Any | Assertion Failure in /mysql-8.0.34/sql/sql_base.cc:9133 |
4065 | 2004-06-08 21:31 | 2020-01-31 13:38 | MySQL Server: DML | Won't fix (1519 days) | S4 | all | Any (all) | Any | remove the need to mention column name in select in order to use it in having |
36084 | 2008-04-15 8:34 | 2012-05-18 20:19 | MySQL Server: DML | Duplicate (5827 days) | S3 | 5.0.58 | Any | Any | name_const with negative, subquery, group by causes crash |
38928 | 2008-08-20 21:58 | 2008-08-20 22:52 | MySQL Server: DML | Not a Bug (5700 days) | S2 | 5.0.67-community-nt | Windows (XP SP2) | Any | select ... count(*) not enforcing group by clause when obtaining other fields |
39543 | 2008-09-19 16:56 | 2018-02-10 16:42 | MySQL Server: DML | Closed (2239 days) | S3 | 5.0.67/5.1/6.0 | Linux (debian 4.0) | Any | Group by with case and lpad inside concat truncates values |
39656 | 2008-09-26 2:15 | 2011-02-16 23:43 | MySQL Server: DML | Closed (5590 days) | S1 | 5.0.67, 5.1.28 | Any (Windows XP, Fedora 9) | Any | Behaviour different for agg functions with & without where - ONLY_FULL_GROUP_BY |
42009 | 2009-01-10 1:44 | 2011-02-16 23:43 | MySQL Server: DML | Closed (5391 days) | S2 | 5.1.30-log, 4.1, 5.0, 5.1, 6.0 bzr | Linux (Ubuntu 8.10 with 2.6.27-9-generic kernel) | Any | SELECT into variable gives different results to direct SELECT |
47434 | 2009-09-18 10:18 | 2018-09-09 20:45 | MySQL Server: DML | Verified (5301 days) | S3 | 5.0.51a-24+lenny1-log, 5.1.38 | Linux | Any | Ambigous field name in group by clause does not cause an error |
56514 | 2010-09-02 18:00 | 2018-02-11 12:57 | MySQL Server: DML | Can't repeat (2238 days) | S3 | 5.5.5 m3 | FreeBSD (7.2) | Any | Mixing utf8, group by, IF and Datefield cause a truncate problem (Only in views) |
65706 | 2012-06-22 7:42 | 2013-01-10 12:16 | MySQL Server: DML | Can't repeat (4096 days) | S1 | 5.5.24, 5.5.27, 5.1.65, 5.0.97 | Linux (Ubuntu 12.04) | Any | SELECT statement used to create a view works, selecting from the view -> ER 1356 |
65970 | 2012-07-20 21:50 | 2012-07-23 10:02 | MySQL Server: DML | Verified (4269 days) | S3 | 5.5.19, 5.5.26 | Any | Any | AVG group function when dealing with maximum number give wrong results |
65983 | 2012-07-23 10:41 | 2012-08-24 1:00 | MySQL Server: DML | No Feedback (4236 days) | S2 | 5.1.40 | Linux | Any | a executing subquery , never stop |
67529 | 2012-11-09 0:20 | 2017-01-09 18:55 | MySQL Server: DML | Verified (4158 days) | S3 | 5.1.41, 5.1.67, 5.5.29, 5.7.0 | Any | Any | GROUP BY treats +0 and -0 as different values |
69310 | 2013-05-23 11:47 | 2018-03-14 20:45 | MySQL Server: DML | Verified (3963 days) | S3 | 5.6, 5.0.97, 5.1.70, 5.5.32, 5.6.12, 5.7.2 | Any | Any | Valid SQL statement rejected in ONLY_FULL_GROUP_BY |
71244 | 2013-12-30 9:48 | 2014-03-29 8:31 | MySQL Server: DML | Closed (3678 days) | S2 | 5.6.15, 5.5.35, 5.1.72, 5.7.3 | Any | Any | Wrong result computation using ALL() and GROUP BY |
72098 | 2014-03-21 20:47 | 2019-11-18 22:37 | MySQL Server: DML | Closed (1593 days) | S3 | 5.5, 5.5.38 | Any | Any | select * from (subquery) get different result with subquery. |
76468 | 2015-03-24 0:06 | 2015-03-25 5:09 | MySQL Server: DML | Duplicate (3292 days) | S1 | 5.6.22, 5.5.44, 5.6.23, 5.6.25 | Any | Any | void Item_row::illegal_method_call(const char*): Assertion `0' failed. |
77194 | 2015-05-29 17:10 | 2015-06-19 12:58 | MySQL Server: DML | Duplicate (3206 days) | S3 | 5.6.23 | Linux (CentOS 7) | Any | Assertion `param.sort_length != 0' failed in sql/filesort.cc:361 |
77632 | 2015-07-06 19:07 | 2015-08-26 13:29 | MySQL Server: DML | Closed (3138 days) | S2 | 5.7.7 | Linux | Any | count distinct returns in-correct result |
78181 | 2015-08-24 6:59 | 2015-08-24 9:23 | MySQL Server: DML | Verified (3140 days) | S2 | 5.6.21, 5.6.26, 5.7.9 | Any | Any | Group by different behavior in mysql 5.6.21 |
78330 | 2015-09-05 0:12 | 2015-09-05 6:34 | MySQL Server: DML | Duplicate (3128 days) | S1 | 5.6.23 | Any | Any | handle_fatal_signal (sig=6) in Item_row::illegal_method_call on SELECT |
78360 | 2015-09-08 6:14 | 2015-09-08 12:29 | MySQL Server: DML | Verified (3125 days) | S3 | 5.6.22, 5.6.26 | Any | Any | More than 1 row is returned when using "having count(alias)" |
78508 | 2015-09-22 3:20 | 2015-09-22 12:19 | MySQL Server: DML | Not a Bug (3111 days) | S3 | 5.6.22 | Any | Any | Subquery result with aggregate function() in outer table is not understandable |
81024 | 2016-04-09 19:53 | 2016-04-09 21:45 | MySQL Server: DML | Verified (2911 days) | S5 | 5.0/5.1/5.5/5.6/5.7 | Windows (Microsoft Windows 7 Enterprise Service Pack 1) | Any | HAVING without GROUP BY should imply an aggregation of a single group |
81450 | 2016-05-17 5:28 | 2019-12-16 22:33 | MySQL Server: DML | Closed (1565 days) | S6 | 5.5.49 | Any | Any | void make_sortkey(SORTPARAM*, uchar*, uchar*): Assertion `0' failed make_sortkey |
81684 | 2016-06-02 6:05 | 2016-06-02 13:22 | MySQL Server: DML | Verified (2857 days) | S1 | 5.7.8, 5.6.30, 5.7.12 | Any | Any | select + where exists( select + group by + limit) works incorrectly |
84030 | 2016-12-01 18:40 | 2017-01-02 1:00 | MySQL Server: DML | No Feedback (2644 days) | S3 | 5.6.34 | Linux | Any | Duplicate entry error when doing GROUP BY with UTF collation |
21728 | 2006-08-18 22:50 | 2018-11-30 3:17 | MySQL Server: DML | Closed (1946 days) | S4 | 4.1.21-win32 | Windows (Windows XP) | Any | MySQL Rollup Testing and check failure |
27795 | 2007-04-12 22:26 | 2018-09-09 20:45 | MySQL Server: DML | Verified (6196 days) | S4 | 5.0.40, 5.1 | Any | Any | patch for explain extended to show outer aggregates like outer fields |
28957 | 2007-06-07 19:30 | 2015-10-22 19:36 | MySQL Server: DML | Verified (6138 days) | S4 | 5.x | Any | Any | Ordered Analytical Functions |
31000 | 2007-09-13 12:52 | 2011-02-16 23:43 | MySQL Server: DML | Closed (5265 days) | S2 | 5.0.45 | Windows | Any | Left join using stored function fails with corrupted result |
31063 | 2007-09-17 15:58 | 2007-09-18 11:34 | MySQL Server: DML | Can't repeat (6037 days) | S3 | 5.1.21 | Any | Any | GROUP BY WITH ROLLUP inconsistence with derived tables |
31472 | 2007-10-09 8:59 | 2012-05-18 20:19 | MySQL Server: DML | Duplicate (5899 days) | S3 | 5.0.50 | Any | Any | multi_update crashes at assert about trans_safe |
32030 | 2007-11-01 12:55 | 2007-12-14 19:47 | MySQL Server: DML | Closed (5950 days) | S3 | Any | Any | DELETE does not return an error and deletes rows if error evaluating WHERE | |
33254 | 2007-12-14 22:56 | 2007-12-16 19:01 | MySQL Server: DML | Not a Bug (5948 days) | S1 | mysql 5.0.27 | FreeBSD (6.2) | Any | Invalid query: Unknown column 'column_id' in 'on clause' |
33304 | 2007-12-17 23:50 | 2008-03-27 19:29 | MySQL Server: DML | Closed (5846 days) | S3 | 5.0.54 | MacOS (10.4 PowerPC 64-bit) | Any | Test 'func_group' hangs on Mac OS X 10.4 PowerPC 64-bit |
33647 | 2008-01-03 10:16 | 2013-05-16 6:10 | MySQL Server: DML | Not a Bug (3970 days) | S3 | 5.1.22 | Any | Any | WITH ROLLUP fails when using subqueries |
34755 | 2008-02-22 8:06 | 2008-02-22 9:41 | MySQL Server: DML | Not a Bug (5880 days) | S2 | 5.0.45 SUSE MySQL RPM and 5.0.51a-commun | Linux (opensuse 10.3) | Any | error in select statement with joins - unknown column |
36138 | 2008-04-16 13:21 | 2008-04-25 12:06 | MySQL Server: DML | Not a Bug (5817 days) | S1 | 5.0.45 | Any | Any | SELECT with LEFT JOIN and aggregate function returns incorrect results |
36791 | 2008-05-19 1:10 | 2008-06-19 16:45 | MySQL Server: DML | No Feedback (5762 days) | S2 | 5.1.23 | Windows | Any | Error trying to get Column Names |
37055 | 2008-05-29 6:09 | 2008-06-30 15:29 | MySQL Server: DML | No Feedback (5751 days) | S2 | 5.0.18 | Linux | Any | sub query with in condition takes long time and it hangs |
38091 | 2008-07-14 5:14 | 2008-08-07 4:19 | MySQL Server: DML | Not a Bug (5713 days) | S3 | 5.1.23 | Windows (Vista Enterprise) | Any | LOAD DATA LOCAL INFILE using source column references loads sequential columns |
20071 | 2006-05-25 18:27 | 2006-06-02 5:40 | MySQL Server: Documentation | Closed (6510 days) | S3 | 5.1.12 | Linux (Linux 32 Bit OS) | Any | LOGFILE_GROUP_NAME in on-line docs needs to be corrected |
20817 | 2006-07-03 1:32 | 2006-07-04 15:12 | MySQL Server: Documentation | Closed (6478 days) | S3 | 5.0.22 | Solaris (Solaris) | Any | package not install: user "mysql" not found |
23737 | 2006-10-27 21:09 | 2007-03-15 0:31 | MySQL Server: Documentation | Closed (6224 days) | S2 | 5.1.13 bk | Linux (ubuntu dapper drake) | Any | CREATE TABLESPACE without INITIAL_SIZE creates datafile with random size |
26635 | 2007-02-26 13:03 | 2007-03-07 17:52 | MySQL Server: Documentation | Closed (6232 days) | S3 | all | Any (all) | Any | CREATE table and password |
26990 | 2007-03-09 9:14 | 2007-03-09 10:45 | MySQL Server: Documentation | Closed (6230 days) | S3 | Any | Typo in 5.1 Documentation Chapter 13.1.9. | ||
28155 | 2007-04-29 22:37 | 2007-05-02 15:12 | MySQL Server: Documentation | Closed (6176 days) | S3 | Any | Any | Any | Some aggregate functions don't appear in TOC |
30170 | 2007-08-01 7:09 | 2007-09-06 17:40 | MySQL Server: Documentation | Closed (6049 days) | S3 | 5.0.37, 5.0.42 | Linux (RHEL4) | Any | Query optimization depends on too many undocumented(!) factors |
34943 | 2008-02-28 21:43 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5064 days) | S3 | 5.1.23 | Any | Any | effect of combining SQL_%_RESULT modifiers and use in subqueries should be doc'd |
35010 | 2008-03-03 18:49 | 2008-11-26 17:07 | MySQL Server: Documentation | Closed (5602 days) | S3 | Any | Any | View mergeability criteria are incorrect in the documentation | |
35163 | 2008-03-08 16:04 | 2008-10-30 17:57 | MySQL Server: Documentation | Closed (5629 days) | S3 | 5.0.32 | Linux | Any | memlock make raw disk partition unaccessable |
36476 | 2008-05-02 15:17 | 2008-05-20 15:17 | MySQL Server: Documentation | Closed (5792 days) | S2 | 5.0.37-log / i686 | Linux (Slackware ~11) | Any | Bin log file changed ownership after password reset |
6818 | 2004-11-25 1:42 | 2004-11-26 7:35 | MySQL Server: Documentation | Closed (7063 days) | S3 | 4.1.7 | Any | undocumented change in alias behavior | |
9612 | 2005-04-04 14:16 | 2005-04-07 1:30 | MySQL Server: Documentation | Closed (6931 days) | S2 | v4.0.21 | Linux (Linux tcas02 2.4.21-226-smp #1 S) | Any | Column type DOUBLE fails to store input correctly, but TEXT does... |
11375 | 2005-06-16 10:57 | 2020-11-22 20:45 | MySQL Server: Documentation | No Feedback (6678 days) | S2 | Any | Unbalanced data for number of nodes not on the form 2 ** n | ||
11829 | 2005-07-09 2:19 | 2005-07-11 14:06 | MySQL Server: Documentation | Closed (6836 days) | S3 | Any | D.1.3. Changes in release 5.0.8 - bad example code | ||
12121 | 2005-07-22 18:57 | 2005-09-09 17:30 | MySQL Server: Documentation | Closed (6776 days) | S3 | Any | C-API: mysql_real_connect documentation is not exact | ||
12738 | 2005-08-23 0:09 | 2005-09-01 17:43 | MySQL Server: Documentation | Closed (6784 days) | S3 | > 4.1.10, > 5.0.2 | Linux (Linux/Windows) | Any | DOUBLE type column doesnot store the values as described in the manual |
13088 | 2005-09-09 13:35 | 2005-09-09 17:17 | MySQL Server: Documentation | Closed (6776 days) | S3 | Any | Documentation Bug for the ENUM field | ||
16109 | 2005-12-30 23:35 | 2006-01-05 15:45 | MySQL Server: Documentation | Closed (6658 days) | S3 | n/a | n/a | Any | doubled words in 5.0.17 manual |
81342 | 2016-05-06 22:22 | 2018-06-26 2:40 | MySQL Server: Documentation | Not a Bug (2103 days) | S3 | 5.7.11 | CentOS | Any | Using ONLY_FULL_GROUP_BY rejects statements in MySQL 5.7 but not in MySQL 5.6 |
81792 | 2016-06-09 22:00 | 2018-11-05 12:57 | MySQL Server: Documentation | Not a Bug (1974 days) | S3 | 5.7.13 | Any | Any | ONLY_FULL_GROUP_BY not reject queries with aggregate functions without group by |
82075 | 2016-07-01 1:03 | 2016-07-20 23:57 | MySQL Server: Documentation | Closed (2809 days) | S3 | Any | Any | sakila sample DB has a MyISAM table | |
82505 | 2016-08-09 11:36 | 2019-03-05 13:13 | MySQL Server: Documentation | Closed (1950 days) | S1 | 5.7.14 | Ubuntu (16.04) | Any | discarding tablespace head to inconsistence cluster and terminating nodes |
82740 | 2016-08-26 8:09 | 2017-02-11 14:57 | MySQL Server: Documentation | Closed (2603 days) | S3 | Any | Any | Documentation for "HAVING" is missing | |
82900 | 2016-09-08 6:18 | 2016-09-15 15:00 | MySQL Server: Documentation | Not a Bug (2752 days) | S3 | 5.6 | Any | Any | Discrepancy in sync_binlog parameter documentation |
84303 | 2016-12-21 18:23 | 2018-05-30 12:51 | MySQL Server: Documentation | Closed (2130 days) | S3 | 5.7.17 | Any | Any | Steps for user and recovery channel missing on creation of first node in docs |
86011 | 2017-04-20 1:28 | 2017-05-15 16:30 | MySQL Server: Documentation | Closed (2510 days) | S3 | 8.0 | Any | Any | Grammatical solecism in 8.0 manual |
99132 | 2020-03-31 14:54 | 2020-10-30 20:22 | MySQL Server: Documentation | Not a Bug (1452 days) | S3 | 8.0.19 | Linux | Any | Group Replication Relay Node documentation is missing |
104024 | 2021-06-15 9:42 | 2021-06-16 22:18 | MySQL Server: Documentation | Closed (1017 days) | S3 | 8.0 | Any | Any | Example in 8.2.1.1 WHERE Clause Optimization is incompatible only_full_group_by |
107464 | 2022-06-02 10:29 | 2022-06-02 13:04 | MySQL Server: Documentation | Not a Bug (666 days) | S3 | 5.7, 8.0 | Any | Any | External Locking for innodb tables |
63919 | 2012-01-04 13:02 | 2012-01-09 13:39 | MySQL Server: Documentation | Closed (4466 days) | S2 | any | Any | Any | concat() and concat_ws() may return NULL in not-documented circumstance- |
68589 | 2013-03-06 23:02 | 2013-04-02 11:53 | MySQL Server: Documentation | Closed (4014 days) | S3 | 5.6.10 | Any | Any | "Using GTIDs for Failover and Scaleout" seems flawed and misleading |
69761 | 2013-07-17 0:35 | 2016-02-25 12:24 | MySQL Server: Documentation | Closed (3908 days) | S3 | 5.6.12 | Any | Any | P_S.HOSTS table contents include NULL hosts |
74464 | 2014-10-20 19:55 | 2015-03-24 23:19 | MySQL Server: Documentation | Closed (3364 days) | S2 | Any | Any | Manual for binlog crash recovery outdated | |
74712 | 2014-11-06 12:09 | 2017-04-11 23:27 | MySQL Server: Documentation | Closed (2544 days) | S3 | Any | Any | Wrong security info in LOAD DATA INFILE documentation | |
74773 | 2014-11-10 22:37 | 2014-11-13 16:15 | MySQL Server: Documentation | Closed (3424 days) | S3 | 5.5, 5.6,5.7 | Any | Any | Explain documentation needs update for Select tables optimized away |
75395 | 2015-01-02 14:46 | 2018-07-25 17:16 | MySQL Server: Documentation | Closed (2074 days) | S4 | 5.7.5 | Any | Any | Explain relation between slave_preserve_commit_order and binlog_order_commit. |
79808 | 2015-12-29 17:50 | 2016-03-09 15:20 | MySQL Server: Documentation | Closed (2942 days) | S3 | any | Any | Any | Manual does NOT explain when "Select tables optimized away" is possible (or not) |
111506 | 2023-06-21 3:46 | 2023-06-21 7:25 | MySQL Server: Documentation | Verified (282 days) | S3 | 5.7.42, 8.0.33 | Any | Any | Spatial index cardinality equals to the number of rows of the table. |
111590 | 2023-06-27 19:37 | 2023-06-28 23:14 | MySQL Server: Documentation | Closed (275 days) | S3 | 8.0, 5.7 | Any | Any | Switched links on documentation page |
109020 | 2022-11-07 20:50 | 2022-11-09 12:18 | MySQL Server: Documentation | Verified (507 days) | S3 | 8.0 | Any | Any | Inconsistent resolution of alias references in order by clause |
112075 | 2023-08-15 15:09 | 2024-03-22 11:14 | MySQL Server: Documentation | Closed (7 days) | S3 | 8.0 | Any | Any | innodb_cached_indexes.n_cached_pages reports crazy high numbers |
113503 | 2023-12-24 7:38 | 2024-02-14 17:25 | MySQL Server: Documentation | Verified (44 days) | S3 | 8.0 | Any | Any | Error in semisynch diagram |
19103 | 2006-04-14 13:04 | 2007-10-09 18:03 | MySQL Server: Documentation | Closed (6016 days) | S3 | 5.0 | Any | Any | --defaults-group-suffix not documented |
20284 | 2006-06-06 7:57 | 2006-07-27 2:47 | MySQL Server: Documentation | Closed (6455 days) | S4 | 5.0.20 | Any (All) | Any | There is no description of "copying to group table" |
25696 | 2007-01-18 15:22 | 2007-03-05 19:54 | MySQL Server: Documentation | Closed (6234 days) | S4 | Any | Alternatives to rows with group-wise maximum | ||
27177 | 2007-03-15 15:14 | 2007-07-03 15:05 | MySQL Server: Documentation | Closed (6114 days) | S3 | All Versions | Any | Any | SHOW PROCESSLIST Syntax - add descriptions for state |
27278 | 2007-03-19 23:47 | 2007-03-20 17:57 | MySQL Server: Documentation | Closed (6219 days) | S3 | 5.0 | Any (*) | Any | aggregate of outer query for subquery not documented |
29317 | 2007-06-23 13:42 | 2007-06-25 13:05 | MySQL Server: Documentation | Closed (6122 days) | S3 | 5.0 | Any | Any | COUNT() listed in other functions |
33520 | 2007-12-27 0:29 | 2008-07-31 17:19 | MySQL Server: Documentation | Closed (5720 days) | S3 | 5.1.22 | Any | Any | Description for UDF aggregate function XXX_add not correct |
18131 | 2006-03-10 11:03 | 2006-03-28 17:26 | MySQL Server: Documentation | Not a Bug (6576 days) | S1 | MySQL 5.0.18 | Windows (Windows XP & Linux Fedora core 4) | Any | GROUP BY doesn't always work |
46567 | 2009-08-05 14:24 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5348 days) | S3 | 5.0, 5.1, 5.4/6.0 | Any | Any | Aggregate function documentation needs clarification for non-GROUP BY behavior |
73582 | 2014-08-14 12:18 | 2014-09-29 16:48 | MySQL Server: Documentation | Closed (3469 days) | S3 | 5.6 5.7 | Any | Any | Documentation says group commit for the binary log works only if sync_binlog=0 |
79100 | 2015-11-03 17:01 | 2015-11-17 18:52 | MySQL Server: Documentation | Closed (3055 days) | S3 | any, 5.5, 5.6, 5.7 | Any | Any | MySQL Manual does not explain when ORDER BY NULL does NOT prevent filesort |
82544 | 2016-08-11 14:36 | 2016-08-17 14:57 | MySQL Server: Documentation | Closed (2781 days) | S3 | 5.7.14 | Any | Any | Duplicate entry '' for key '<group_key>' while doing group by |
84631 | 2017-01-24 1:38 | 2019-01-03 11:45 | MySQL Server: Documentation | Closed (1912 days) | S3 | 5.7 | Any | Any | Group Replication Installation Documentation |
85977 | 2017-04-18 2:02 | 2018-11-02 15:03 | MySQL Server: Documentation | Verified (2537 days) | S3 | 5.7 and 8.0 | Any | Any | The doc. of slave-parallel-type=LOGICAL_CLOCK wrongly reference Group Commit. |
90553 | 2018-04-21 10:46 | 2019-07-11 7:55 | MySQL Server: Documentation | Closed (1723 days) | S3 | 8.0.11 | Any | Any | group replication installation docs lead to errors in the logs |
108821 | 2022-10-19 10:01 | 2022-11-16 13:46 | MySQL Server: Documentation | Closed (499 days) | S3 | 8.0.31 | Any | Any | DOC issue with group_replication_communication_debug_options description |
13863 | 2005-10-08 14:02 | 2006-01-25 20:03 | MySQL Server: Documentation | Closed (6638 days) | S3 | 5.0.13 | Windows (Win XP Professional SP2) | Any | Alternative INTO OUTFILE syntax not documented |
19206 | 2006-04-19 22:02 | 2006-05-02 21:59 | MySQL Server: Documentation | Closed (6541 days) | S2 | 5.1 | Linux (Linux) | Any | Engine hangs trying to read from table that was locked for writing |
29530 | 2007-07-03 20:15 | 2007-07-27 12:59 | MySQL Server: Documentation | Closed (6090 days) | S3 | 5.1 | Any | Any | undocumented options in 'create logfile group' & 'create tablespace' statements |
88005 | 2017-10-06 4:39 | 2019-05-16 14:59 | MySQL Server: Documentation | Closed (1779 days) | S3 | 5.7 | Any | Any | Figure 17.13 seems incorrect in group replication document |
93551 | 2018-12-11 5:18 | 2019-05-15 12:30 | MySQL Server: Documentation | Duplicate (1780 days) | S4 | 8.0.13 | CentOS (7.3) | Any | mysql database seems corrupted if forget loading group_replication plugin |
94014 | 2019-01-23 9:11 | 2019-07-25 11:22 | MySQL Server: Documentation | Closed (1709 days) | S3 | 5.7 | Any | Any | Primary / Secondary role not shown in P_S.replication_group_members |
97734 | 2019-11-21 14:19 | 2020-03-05 7:08 | MySQL Server: Documentation | Verified (1485 days) | S3 | 5.7.27 | Linux | x86 (x86_64) | Document the correct method to stop slaving with MTS without a warning or error |
101111 | 2020-10-10 2:30 | 2021-03-02 13:05 | MySQL Server: Documentation | Closed (1263 days) | S3 | Any | Any | document bug | |
101514 | 2020-11-09 4:46 | 2020-11-13 16:30 | MySQL Server: Documentation | Closed (1232 days) | S3 | 5.7, 8.0 | Any | Any | The requirements of Group Replication is not complete. |
101515 | 2020-11-09 4:50 | 2021-04-08 12:38 | MySQL Server: Documentation | Closed (1086 days) | S3 | 5.7, 8.0 | Any | Any | The requirements of Group Replication are not complete. |
101521 | 2020-11-09 7:35 | 2020-11-10 17:36 | MySQL Server: Documentation | Not a Bug (1235 days) | S3 | 5.7 | Any | Any | The user/group permission should be specified about system variable 'datadir' |
106623 | 2022-03-02 22:01 | 2022-03-03 22:17 | MySQL Server: Documentation | Closed (757 days) | S3 | 8.0 | Any | Any | Incorrect multi-index hint example |
111095 | 2023-05-21 9:42 | 2023-05-22 12:43 | MySQL Server: Documentation | Unsupported (312 days) | S3 | Any | Any | Enhance film_list view by GROUP_CONCATing category.name column values | |
112001 | 2023-08-09 3:27 | 2023-08-11 16:14 | MySQL Server: Documentation | Closed (231 days) | S3 | 8.0, 8.1 | Any | Any | Wrong Authorized User |
265 | 2003-04-09 18:04 | 2003-04-10 4:01 | MySQL Server: Documentation | Closed (7659 days) | S3 | Any | misspelling of SEPARATOR in documentation | ||
36879 | 2008-05-22 8:32 | 2008-05-23 12:37 | MySQL Server: Documentation | Closed (5789 days) | S3 | 5.0.51a-3ubuntu5.1-log | Linux (Kubuntu 8.04) | Any | mysql monitor "help max" and "help min" provider no help but "help min max" does |
42319 | 2009-01-24 6:32 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5542 days) | S3 | 5.1.30 / NDB 6.3.20 | Any | Any | ALTER LOGFILE GROUP is not in online help |
53587 | 2010-05-11 22:57 | 2016-08-17 14:51 | MySQL Server: Documentation | Closed (2781 days) | S3 | 5.0,5.1 | Any | Any | what are the semantics of the rand function |
59574 | 2011-01-18 7:00 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (4810 days) | S3 | 5.1.51 | FreeBSD (Server version: 5.1.51 FreeBSD port: mysql-server-5.1.51_1) | Any | Assignment operator with group functions |
63922 | 2012-01-04 15:05 | 2013-04-10 1:41 | MySQL Server: Documentation | Won't fix (4006 days) | S1 | 14.14 Distrib 5.5.16, for Linux (x86_64) | Linux (3.1.1) | Any | Order by null dosn't change sorting of grouped result |
69439 | 2013-06-11 9:00 | 2013-06-11 14:15 | MySQL Server: Documentation | Closed (3944 days) | S3 | 5.1.70, 5.5.32 | Any | Any | Documented minimal value of innodb_log_file_size is wrong in 5.1 and 5.5 |
71189 | 2013-12-20 14:56 | 2021-08-08 20:45 | MySQL Server: Documentation | Verified (3752 days) | S3 | 5.5, any | Any | Any | Manual does not provide enough details on how loose index scan really works |
83128 | 2016-09-23 11:04 | 2017-01-24 14:35 | MySQL Server: Documentation | Closed (2621 days) | S3 | 0.9.0-labs | Linux | Any | Group Replication depends on resolvable hostnames without domain |
74095 | 2014-09-26 8:04 | 2014-10-27 14:04 | MySQL Server: Documentation | Closed (3441 days) | S3 | mysql 5.7.5m15 | Any | Any | "MySQL Extensions to GROUP BY" documentation needs update |
74093 | 2014-09-26 7:18 | 2014-09-30 17:54 | MySQL Server: Documentation | Closed (3468 days) | S3 | 5.7.5m15 | Any | Any | ONLY_FULL_GROUP_BY documentation not up to date |
70203 | 2013-08-30 16:38 | 2013-08-31 12:32 | MySQL Server: Documentation | Not a Bug (3863 days) | S3 | 5.5.32 | Any | Any | GROUP BY is consistent with ORDER BY in subquery |
33655 | 2008-01-03 16:06 | 2008-07-31 17:19 | MySQL Server: Documentation | Closed (5720 days) | S3 | Any | Any | UDF documentation is unclear on pre-5.0 and 5.0 differences | |
36798 | 2008-05-19 13:05 | 2008-06-12 15:33 | MySQL Server: Documentation | Closed (5769 days) | S2 | 5.1.23/5.1.24 | Any | Any | aggregate functions with columns and aggregate functions works (shouldn't?) |
15643 | 2005-12-09 18:42 | 2006-09-06 19:12 | MySQL Server: Documentation | Closed (6414 days) | S2 | 5.0.15/5.0.18 BK/5.0.22 | Any (All) | Any | Can't group on calculated field aliased as other field |
45809 | 2009-06-28 15:18 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5333 days) | S3 | 5.1.35-community,5.1.36-community | Windows (XP Pro) | Any | Use "COUNT()" without "GROUP BY" has no error message |
103766 | 2021-05-21 11:35 | 2022-03-16 11:36 | MySQL Server: Documentation | Verified (1043 days) | S4 | 8.0 | Any | Any | please document external (network) protocol used by group replication |
110888 | 2023-05-02 18:51 | 2023-07-31 15:35 | MySQL Server: Documentation | Closed (242 days) | S3 | 8.0.31 | Any | Any | checkInstanceConfiguration and docs disagree on binlog_transaction_dependency_tr |
33170 | 2007-12-12 15:45 | 2008-07-30 13:14 | MySQL Server: Documentation | Closed (5721 days) | S3 | 6.0.5 | Any | Any | New CREATE TABLESPACE behavoir with Falcon |
35628 | 2008-03-28 1:41 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5625 days) | S3 | 5.0.52 | Any | Any | 5.0.52+ undocumented incompatible change in default GROUP BY behavior |
83142 | 2016-09-25 18:38 | 2017-02-11 14:38 | MySQL Server: Documentation | Closed (2603 days) | S3 | 5.7.15 | Any | Any | Documentation clarifications about how default option files are used |
88717 | 2017-11-30 14:10 | 2019-02-15 15:08 | MySQL Server: Documentation | Closed (1869 days) | S3 | 5.7.19 | Any | Any | MySQL Group Replication Large Transactions Limit |
102706 | 2021-02-23 15:02 | 2021-03-13 23:18 | MySQL Server: Documentation | Closed (1112 days) | S3 | 8.0.21, 8.0.23 | Any | Any | Update group replication docs replication configuration requirements |
40163 | 2008-10-20 8:41 | 2008-11-26 16:54 | MySQL Server: Documentation | Closed (5602 days) | S3 | 6.0.7, 5.1.29, 5.0.70 | Any | Any | mysql's help is confusing when trying to get information about storage engines |
41768 | 2008-12-27 21:42 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5555 days) | S3 | any | Any | Any | Query with SELECT *, GROUP BY and AGGREGATE |
44666 | 2009-05-05 11:34 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5433 days) | S3 | 5.1, 6.0 | Any | Any | Documentation of mysqld_safe is inexact about options |
44879 | 2009-05-14 16:01 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5430 days) | S5 | Any | Any | bug found in left join example | |
48102 | 2009-10-16 0:16 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5274 days) | S3 | 5.1 | Linux | Any | Documentation wrong about COUNT(DISTINCT) in 11.12.1 |
49869 | 2009-12-22 7:45 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5188 days) | S2 | 5.0, 5.1.39 | Any | Any | Group by Yields Incorrect Results with Derived Column Name with Single Quotes |
51058 | 2010-02-10 12:18 | 2014-11-28 14:08 | MySQL Server: Documentation | Closed (5043 days) | S3 | 5.1.37, 5.1.43 | Any | Any | Recognizing agregated columns in HAVING clausule |
53866 | 2010-05-20 18:23 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5061 days) | S3 | 5.1 | Any | Any | Manual Bug: enabling binary log "makes performance about 1% slower." |
36314 | 2008-04-24 11:16 | 2008-04-24 11:47 | MySQL Server: Documentation | Not a Bug (5818 days) | S3 | all | Any | Any | GRANT is missing in SQL documentation |
50910 | 2010-02-04 12:05 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5167 days) | S3 | 5.1+ | Any | Any | confusing docs lines about replication group termination wth stop slave |
82171 | 2016-07-08 19:24 | 2016-07-27 2:20 | MySQL Server: Documentation | Closed (2802 days) | S3 | Any | Any | GROUP BY Optimization clarification | |
84371 | 2016-12-29 19:14 | 2020-02-05 15:52 | MySQL Server: Documentation | Won't fix (1514 days) | S3 | 5.7.17 | Any | Any | Missing documentation for backup/recover when using MySQL Group Replication |
85998 | 2017-04-19 9:02 | 2018-06-06 8:41 | MySQL Server: Documentation | Closed (2123 days) | S3 | 5.7 | Any | Any | SELECT ... FOR UPDATE not listed as possibe limitation with Group Replication |
86993 | 2017-07-09 18:28 | 2017-07-18 20:04 | MySQL Server: Documentation | Closed (2446 days) | S3 | 5.6, 5.7 | Any | Any | Incorrect statement about InnoDB group commit in the manual |
88228 | 2017-10-25 19:22 | 2017-11-15 21:52 | MySQL Server: Documentation | Closed (2326 days) | S3 | 8.0 | Any | Any | "ORDER BY Optimization" doc contradiction re: GROUP BY |
89686 | 2018-02-16 7:47 | 2019-04-30 11:04 | MySQL Server: Documentation | Closed (1795 days) | S3 | 5.7, 8.0 | Any | Any | Need to add "offset is provided by server_id and increment is 7" to GR manual. |
94186 | 2019-02-04 8:23 | 2019-05-03 9:20 | MySQL Server: Documentation | Closed (1792 days) | S3 | 5.7 | Any | Any | replication_group_members table's document page is incomplete for server status |
97417 | 2019-10-29 13:33 | 2019-11-05 14:50 | MySQL Server: Documentation | Closed (1606 days) | S3 | 8.0 5.7 | Any | Any | Typo in Group Replication Settings docs |
107599 | 2022-06-20 6:26 | 2022-06-20 7:10 | MySQL Server: Documentation | Verified (648 days) | S4 | 8.0 | Any | Any | Improve GR server throttling documentation to provide more details |
3405 | 2004-04-06 22:04 | 2004-04-07 7:15 | MySQL Server: Documentation | Closed (7296 days) | S3 | 5 | Any | No explanation of "formula" for Group By/Order By in Select | |
96479 | 2019-08-08 20:50 | 2019-11-07 2:56 | MySQL Server: Japanese Documentation | Verified (1694 days) | S3 | 5.6 | Any | Any | JapaneseDocumentBug |
102961 | 2021-03-13 14:31 | 2021-04-24 15:49 | MySQL Server: Japanese Documentation | Closed (1070 days) | S3 | 8.0.23 | Any | Any | 1.3 MySQL 8.0 の新機能(レプリケーション~) |
104358 | 2021-07-20 8:35 | 2021-07-20 10:00 | MySQL Server: Japanese Documentation | Verified (983 days) | S3 | 8.0 | Any | Any | typo in documents |
102886 | 2021-03-09 13:21 | 2021-04-24 15:40 | MySQL Server: Japanese Documentation | Closed (1070 days) | S3 | 8.0.23 | Any | Any | 1.3 MySQL 8.0 の新機能(リソース管理~) |
104023 | 2021-06-15 9:15 | 2021-06-15 9:35 | MySQL Server: Japanese Documentation | Verified (1018 days) | S3 | 8.0 | Any | Any | Wrong translation in 8.2.1.1 WHERE 句の最適化 |
85887 | 2017-04-10 23:18 | 2017-04-11 15:11 | MySQL Server: Document Store: MySQL Shell | Verified (2544 days) | S3 | 1.0.8RC | CentOS (6) | Any | AdminAPI error not descriptive for dba.checkInstanceConfiguration |
83246 | 2016-10-03 13:43 | 2018-04-04 17:47 | MySQL Server: Document Store: MySQL Shell | Won't fix (2186 days) | S4 | 5.7.15-labs-gr090 | Any | Any | Improve dba.validateInstance() error output to include my.cnf format |
54407 | 2010-06-10 19:45 | 2010-06-10 20:43 | MySQL Server: Errors | Not a Bug (5041 days) | S1 | Any | Any | My SQL frequent errors# 144, 2006 | |
58775 | 2010-12-07 0:55 | 2010-12-07 4:19 | MySQL Server: Errors | Not a Bug (4861 days) | S3 | 5.1.52 | Any | Any | Table Field Name - Group |
21403 | 2006-08-01 19:21 | 2011-02-16 23:43 | MySQL Server: Errors | Verified | S4 | all | Any (all) | Any | more specific SQL states for 23nnn |
30936 | 2007-09-10 15:19 | 2007-09-10 15:33 | MySQL Server: Errors | Not a Bug (6045 days) | S3 | MySQL 5.0 | Any | Any | Syntax error |
27513 | 2007-03-29 8:47 | 2007-06-27 13:17 | MySQL Server: Errors | Closed (6120 days) | S1 | 5.0.26, 5.0.34, 5.0.40-debug | Linux (Gentoo Linux) | Any | mysql 5.0.x + NULL pointer DoS |
60973 | 2011-04-25 16:37 | 2011-05-25 23:00 | MySQL Server: Errors | No Feedback (4692 days) | S3 | 5.2 | Windows (Error Code 2013 and 2006) | Any | Session Timed out |
71476 | 2014-01-25 11:22 | 2014-02-27 1:00 | MySQL Server: Errors | No Feedback (3684 days) | S3 | 5.6 | Linux (debian squeeze) | Any | InnoDB memory consumption with "bad" query |
84419 | 2017-01-05 7:57 | 2017-01-19 7:13 | MySQL Server: Errors | Verified (2626 days) | S4 | 5.7 | Any | Any | Improve error reporting for external plugin requirement error messages |
86562 | 2017-06-02 13:41 | 2017-11-17 15:08 | MySQL Server: Errors | Closed (2326 days) | S3 | 8.0.2 | Any | Any | SERVER CRASHES IN MY_LOCALE_ERRMSGS::lookup due to INCORRECT option |
108017 | 2022-07-28 18:24 | 2022-08-01 14:18 | MySQL Server: Errors | Verified (606 days) | S4 | 8.0.30 | Any | Any | Init does not provide helpful errors when InnoDB undo/redo log dirs don't exist |
98682 | 2020-02-20 10:27 | 2020-05-29 10:07 | MySQL Server: Errors | Closed (1400 days) | S3 | 8.0.19 | Any | Any | Parameter names in error message are omitted "group_replciation" prefix |
48145 | 2009-10-19 9:39 | 2011-02-16 23:44 | MySQL Server: Errors | Duplicate (5269 days) | S1 | Distrib 5.0.85 | Linux (kernel 2.6.26.7) | Any | ERROR 2013 (HY000) while do mysql-test-run test. |
49514 | 2009-12-07 16:16 | 2013-01-15 16:31 | MySQL Server: Errors | Closed (4091 days) | S2 | 5.1, all | Any | Any | Server crash in recursive call when OOM |
34659 | 2008-02-19 10:36 | 2008-03-11 12:01 | MySQL Server: Errors | Not a Bug (5862 days) | S3 | 5.0+ | Any | Any | Unexpected error & wrong msg.: 1054: Unknown column '...' in 'having clause' |
96579 | 2019-08-18 19:59 | 2019-08-19 22:27 | MySQL Server: Errors | Not a Bug (1684 days) | S3 | 5.6/5.7/8.0 | Any | Any | Unexpected error message when using an outer reference in HAVING |
37344 | 2008-06-11 13:59 | 2008-09-30 20:08 | MySQL Server: Falcon storage engine | Closed (5659 days) | S1 | 6.0-falcon | Any | Any | Crash in IndexWalker::rebalanceDelete |
37343 | 2008-06-11 13:42 | 2008-09-30 19:49 | MySQL Server: Falcon storage engine | Closed (5659 days) | S1 | 6.0-falcon | Any | Any | Assertion in IndexNode::parseNode, ASSERT(key - (UCHAR*) indexNode < 14); |
42341 | 2009-01-26 9:37 | 2009-05-15 16:15 | MySQL Server: Falcon storage engine | Closed (5432 days) | S1 | 6.0-falcon-team | Any | Any | Falcon assertion (key - (UCHAR*) indexNode < 14) in IndexNode::parseNode |
27908 | 2007-04-18 0:46 | 2008-10-07 12:10 | MySQL Server: Falcon storage engine | Can't repeat (5652 days) | S1 | 6.0.0-alpha-pb507 | Any | Any | Server crashes when obtaining data from Falcon's information_schema tables |
32621 | 2007-11-22 12:42 | 2007-12-03 14:27 | MySQL Server: Falcon storage engine | Closed (5961 days) | S3 | 6.0.4 | Any | Any | falcon_ts.test fails |
32993 | 2007-12-05 9:38 | 2008-04-29 17:42 | MySQL Server: Falcon storage engine | Closed (5813 days) | S1 | 6.0.4 | Any | Any | falcon_ts.test fails sporadically |
33824 | 2008-01-11 17:56 | 2008-02-11 21:00 | MySQL Server: Falcon storage engine | Can't repeat (5891 days) | S1 | 6.0.4-p3 | Any | Any | Manipulations on a view and on the underlying table cause duplicate primary key |
33933 | 2008-01-18 20:28 | 2008-10-01 18:09 | MySQL Server: Falcon storage engine | Closed (5658 days) | S1 | 6.0.4-p3-debug | Any | Any | Falcon assertionFailed() in fetchNext() |
35034 | 2008-03-04 14:35 | 2008-09-29 16:46 | MySQL Server: Falcon storage engine | Can't repeat (5660 days) | S3 | 6.0-falcon-team | Any | Any | Falcon crash on complex I_S query in ResultSet::setValue, ResultSet.cpp line 154 |
36603 | 2008-05-08 19:22 | 2009-01-08 9:41 | MySQL Server: Falcon storage engine | Closed (5559 days) | S3 | 6.0.5 | Any | Any | Falcon; Performance drop when ageGroup hits 2^31 |
36734 | 2008-05-15 10:27 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (5428 days) | S1 | 6.0.6pre, 6.0.8pre, 6.0-falcon-team tree | Any | Any | Falcon crash in Record::getEncodedValue |
36971 | 2008-05-26 14:43 | 2008-09-25 20:40 | MySQL Server: Falcon storage engine | Can't repeat (5664 days) | S1 | 6.0-falcon-team | Any | Any | Falcon crash in RecordVersion::fetchVersionRecursive on I_S query |
37577 | 2008-06-23 6:40 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5056 days) | S5 | MySQL6.0 | Linux (SLES10SP1 (2.6.16.46-0.12-smp, x64)) | Any | Query Q9 of DBT3 is running on Falcon slower than Innodb |
37726 | 2008-06-29 12:31 | 2008-10-01 12:42 | MySQL Server: Falcon storage engine | Closed (5658 days) | S1 | 6.0-falcon | Any | Any | Falcon crash in WalkDeferred::getNext |
38043 | 2008-07-11 10:50 | 2008-09-30 20:36 | MySQL Server: Falcon storage engine | Closed (5659 days) | S1 | 6.0-falcon | Any | Any | Deadlock between server and falcon when executing concurrent ALTER + DML |
38044 | 2008-07-11 11:01 | 2008-10-04 13:40 | MySQL Server: Falcon storage engine | Closed (5655 days) | S1 | 6.0-falcon | Any | Any | Falcon crash in StorageTable::compareKey at StorageTable.cpp:412 |
38130 | 2008-07-15 10:35 | 2009-05-15 16:17 | MySQL Server: Falcon storage engine | Closed (5432 days) | S1 | 6.0-falcon | Any | Any | Falcon assertion in IndexNode::expandKey offset + length <= MAX_PHYSICAL_KEY_LEN |
35038 | 2008-03-04 15:40 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5056 days) | S3 | 6.0-falcon-team | Any | Any | Falcon crash on I_S query in RecordVersion::fetchVersion line 98 |
43474 | 2009-03-07 16:55 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (5463 days) | S1 | 6.0-falcon-team | Any | Any | Invalid page number referenced from IndexRootPage::findLeaf() |
38541 | 2008-08-04 14:59 | 2008-12-13 9:05 | MySQL Server: Falcon storage engine | Closed (5585 days) | S1 | 6.0-falcon | Any | Any | Falcon RecordVersion::thaw assertion ""bytesRestored > 0 || data.record == NULL" |
39081 | 2008-08-27 20:45 | 2009-05-15 17:00 | MySQL Server: Falcon storage engine | Closed (5432 days) | S1 | 6.0-falcon, 6.0.7 | Any | Any | Falcon: segfault in StorageInterface::getDemographics() |
40158 | 2008-10-19 20:16 | 2008-12-13 10:04 | MySQL Server: Falcon storage engine | Closed (5585 days) | S1 | 6.0-falcon-team | Any | Any | Falcon assertion in StorageInterface::encodeRecord() line 2635 on CREATE TABLE |
40274 | 2008-10-23 4:37 | 2009-05-15 12:50 | MySQL Server: Falcon storage engine | Closed (5432 days) | S1 | 6.0.8pre, 6.0-falcon-team | Any | Any | Falcon assertion in Transaction::releaseDependencies at Transaction.cpp:792 |
41194 | 2008-12-03 5:43 | 2009-05-15 13:03 | MySQL Server: Falcon storage engine | Closed (5432 days) | S3 | 6.0.8 | Any | Any | Falcon durability should occur earlier in the commit process. |
41661 | 2008-12-20 22:04 | 2009-05-15 13:40 | MySQL Server: Falcon storage engine | Closed (5432 days) | S1 | 6.0-falcon-team | Any | Any | Falcon assertion (ret) failed at line 3052 in file Table.cpp |
42478 | 2009-01-30 13:55 | 2010-05-26 17:59 | MySQL Server: Falcon storage engine | Unsupported (5056 days) | S1 | 6.0-falcon-team | Any | Any | Falcon crash in Database::updateSequence |
42828 | 2009-02-13 12:40 | 2009-05-15 15:10 | MySQL Server: Falcon storage engine | Closed (5432 days) | S1 | 6.0-falcon-team | Any | Any | Falcon crash in Table::checkUniqueRecordVersion - transaction = 0x0 |
42902 | 2009-02-16 19:49 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (5503 days) | S1 | Any | Any | Falcon 100% CPU loop in Index::scanIndex() after recovery | |
43213 | 2009-02-26 8:45 | 2010-05-26 18:00 | MySQL Server: Falcon storage engine | Unsupported (5056 days) | S2 | 6.0.10-alpha | Any | Any | falcon_limit test reports deadlock when locking indexes |
43344 | 2009-03-03 22:14 | 2010-05-26 17:59 | MySQL Server: Falcon storage engine | Unsupported (5056 days) | S2 | 6.0.10-alpa | Any | Any | falcon_recovery assert "dup->state == recDeleted" in Table::checkUniqueRecordVer |
43488 | 2009-03-08 21:22 | 2009-05-15 17:03 | MySQL Server: Falcon storage engine | Closed (5432 days) | S1 | 6.0.11-bzr | Any | Any | Crash in Table::fetchForUpdate (update conflict) when using LIMIT query |
43565 | 2009-03-11 15:51 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (5497 days) | S1 | 6.0.10-release | Any | Any | Falcon: Access to any Falcon data after second restart of server causes crash |
43592 | 2009-03-12 12:48 | 2009-03-12 12:48 | MySQL Server: Falcon storage engine | Duplicate | S3 | 6.0.10-release | Any | Any | Falcon crashes at IndexRootPage.cpp:1131 |
43858 | 2009-03-25 13:34 | 2009-05-15 16:09 | MySQL Server: Falcon storage engine | Closed (5432 days) | S2 | 6.0.11-alpha | Any | Any | falcon_limit crashes in Transaction::visible() |
43958 | 2009-03-30 13:07 | 2009-05-15 16:10 | MySQL Server: Falcon storage engine | Closed (5432 days) | S1 | 6.0.11-bzr | Solaris (Solaris 10 x64) | Any | Assertion (transState != NULL) failed in Transaction::waitForTransaction |
44212 | 2009-04-11 9:22 | 2014-02-21 18:04 | MySQL Server: Falcon storage engine | Unsupported (3689 days) | S1 | 6.0-falcon-team | Any | Any | Falcon infinite loop on SELECT after recovery |
44850 | 2009-05-13 16:08 | 2010-05-26 17:59 | MySQL Server: Falcon storage engine | Unsupported (5056 days) | S3 | 6.0.11 | Any | Any | Falcon; StorageTable::dataStream can point to freed memory |
46324 | 2009-07-21 15:42 | 2010-05-26 18:01 | MySQL Server: Falcon storage engine | Unsupported (5056 days) | S1 | 6.0.12-bzr | Any | Any | Crash during repeated INSERT ... SELECT if falcon debug mask includes 4 |
50556 | 2010-01-22 19:56 | 2013-03-03 20:45 | MySQL Server: FULLTEXT search | Duplicate (5141 days) | S2 | 5.1.42 | Any | Any | full text search hanging |
38150 | 2008-07-15 19:51 | 2008-09-03 17:41 | MySQL Server: FULLTEXT search | No Feedback (5686 days) | S1 | 5.1.25-rc | Linux (Suse 10.3) | Any | match ... against () never returns IN BOOLEAN MODE with characters like "-", "." |
87182 | 2017-07-25 8:27 | 2017-07-31 12:44 | MySQL Server: FULLTEXT search | Verified (2433 days) | S3 | 5.6.35 | Any | Any | Sporadic MATCH AGAINST results with unique index |
68720 | 2013-03-19 16:18 | 2013-06-10 18:05 | MySQL Server: FULLTEXT search | Closed (3945 days) | S3 | 5.6.10, 5.6.12, 5.7.2 | Any | Any | Literal phrases cannot be combined with + or - operator |
107201 | 2022-05-03 18:13 | 2022-05-04 5:52 | MySQL Server: FULLTEXT search | Verified (695 days) | S2 | 8.0.29 | Ubuntu | x86 | Result of fulltext match is on the wrong row with GROUP BY (reproducible) |
84710 | 2017-01-30 8:45 | 2017-11-21 10:21 | MySQL Server: Group Replication | Duplicate (2320 days) | S1 | 5.7.17 | Any | Any | group replication does not respect localhost IP |
84728 | 2017-01-31 8:22 | 2017-07-11 11:08 | MySQL Server: Group Replication | Closed (2453 days) | S2 | 5.7.17 | Any | Any | Not Possible To Avoid MySQL From Starting When GR Cannot Start |
84729 | 2017-01-31 8:39 | 2019-10-30 12:48 | MySQL Server: Group Replication | Closed (1612 days) | S4 | 5.7.17 | Any | Any | Group Replication: Block Reads On Partitioned Nodes |
84730 | 2017-01-31 8:43 | 2017-02-03 12:24 | MySQL Server: Group Replication | Verified (2611 days) | S4 | 5.7.17 | Any | Any | Feature: Troubleshoot Group Replication Transaction Rollbacks |
84733 | 2017-01-31 9:15 | 2017-06-21 11:32 | MySQL Server: Group Replication | Closed (2554 days) | S3 | 5.7.17 | Any | Any | Cannot Start GR with super_read_only=1 |
84784 | 2017-02-02 3:06 | 2019-07-07 6:39 | MySQL Server: Group Replication | Closed (1829 days) | S2 | 5.7.17, 8.0.4 | Any | Any | Group Replication nodes do not rejoin cluster after network connectivity issues |
84785 | 2017-02-02 3:38 | 2017-06-09 9:37 | MySQL Server: Group Replication | Closed (2485 days) | S2 | 5.7.17 | Any | Any | Prevent Large Transactions in Group Replication |
84798 | 2017-02-02 14:32 | 2017-09-22 15:41 | MySQL Server: Group Replication | Closed (2380 days) | S3 | 5.7.17 | Any | Any | Group Replication can use some verbosity in the error log |
86581 | 2017-06-05 4:48 | 2017-06-14 3:37 | MySQL Server: Group Replication | Verified (2480 days) | S4 | 5.7.18 | Any | Any | GCS timeout waiting for executing stop group_replication when loss majority |
86859 | 2017-06-29 4:23 | 2017-12-21 17:47 | MySQL Server: Group Replication | Closed (2290 days) | S2 | 5.7.18 | Any | Any | Group Replication does not honor skip-name-resolve |
86979 | 2017-07-07 7:11 | 2018-04-11 16:07 | MySQL Server: Group Replication | Closed (2179 days) | S3 | mysql5.7.18 | Ubuntu | Any | group replicat master automatically quit |
88414 | 2017-11-09 7:42 | 2018-01-15 12:40 | MySQL Server: Group Replication | Not a Bug (2265 days) | S2 | mysql5.7.20 | Red Hat (7.3) | Any | After online node is restored, the state has not changed to mysql5.7.20 |
88668 | 2017-11-27 17:30 | 2018-05-31 14:49 | MySQL Server: Group Replication | Closed (2227 days) | S3 | 8.0.4 | Any | Any | UNISTALL Group Replication can deadlock with GR Start on server start |
88830 | 2017-12-08 9:55 | 2018-05-31 14:51 | MySQL Server: Group Replication | Closed (2179 days) | S3 | 9.0.0 | Any | Any | With plugin-load and typo debugger aborts with missing DBUG_RETURN in '?func' |
89287 | 2018-01-17 15:49 | 2018-05-31 14:55 | MySQL Server: Group Replication | Closed (2228 days) | S3 | 5.7.21 | Any | Any | Enforce that all members do have the same lower_case_table_names value |
91465 | 2018-06-28 12:20 | 2020-12-28 15:02 | MySQL Server: Group Replication | Can't repeat (2083 days) | S3 | 5.7.20-log | Linux (Red Hat 4.8.5-16) | x86 | network is ok, but GR node been unreachable |
93212 | 2018-11-15 15:34 | 2020-01-20 9:46 | MySQL Server: Group Replication | Closed (1753 days) | S3 | 8.0.13 | Any | Any | Some threads are not registered in the global thread manager |
93784 | 2019-01-02 14:17 | 2020-08-15 1:13 | MySQL Server: Group Replication | Can't repeat (1895 days) | S3 | 8.0.12 | CentOS | x86 | Commit timestamp is more recent than the immediate commit timestamp despite SYNC |
94565 | 2019-03-05 15:45 | 2019-04-18 6:57 | MySQL Server: Group Replication | Closed (1807 days) | S4 | 5.7.25 | Ubuntu | Any | group_replication_member_stats do not have every columns listed in docs |
95306 | 2019-05-08 17:20 | 2019-07-25 8:40 | MySQL Server: Group Replication | Closed (1775 days) | S3 | 8.0.17 | Any | Any | _get_communication_protocol() fails if one or more members are RECOVERING |
96447 | 2019-08-07 10:59 | 2020-01-20 9:56 | MySQL Server: Group Replication | Closed (1605 days) | S3 | 8.0.17 | Any | Any | Group Replication Clone process might conflict with recovery phase 0 |
96758 | 2019-09-04 23:29 | 2023-09-04 6:23 | MySQL Server: Group Replication | Verified (1666 days) | S2 | 8.0.16-7 | Linux | Any | Rollbacks with Foreign Keys on single node |
97101 | 2019-10-04 4:53 | 2020-10-06 11:06 | MySQL Server: Group Replication | Closed (1270 days) | S4 | Any | Any | Allow CREATE TABLE ... SELECT ... to work with group replication | |
97540 | 2019-11-07 17:59 | 2020-01-20 10:02 | MySQL Server: Group Replication | Closed (1599 days) | S3 | 8.0 | Any | Any | errors not showing on ps.replication_applier_status_by_worker on single applier |
97645 | 2019-11-14 16:06 | 2019-12-16 1:00 | MySQL Server: Group Replication | No Feedback (1566 days) | S3 | 8.0.18 | CentOS | Any | Cannot rejoinInstance after a group replication member being expelled |
97800 | 2019-11-26 14:21 | 2020-01-11 1:00 | MySQL Server: Group Replication | No Feedback (1540 days) | S1 | MySQL 8.0.18 | Red Hat (7.4) | x86 | lost binlog when sync-binlog=1 in single primary group replication |
98151 | 2020-01-08 1:03 | 2023-09-12 11:14 | MySQL Server: Group Replication | Can't repeat (199 days) | S3 | 8.0.18 | Any | Any | group replication with wrong member_state after server shutdown |
98473 | 2020-02-04 4:18 | 2020-03-02 10:18 | MySQL Server: Group Replication | Not a Bug (1488 days) | S3 | 8.0.18 | Any | Any | group replication will be block after lock table |
99345 | 2020-04-24 9:03 | 2020-05-13 9:50 | MySQL Server: Group Replication | Closed (1416 days) | S2 | 8.0.19 | Oracle Linux (Official Docker Image : mysql/mysql-server:8.0.19) | x86 | Group replication consistency error when add instance BUG#30394258 not fixed |
101274 | 2020-10-22 11:45 | 2020-11-25 1:00 | MySQL Server: Group Replication | No Feedback (1221 days) | S2 | 8.0.22 | Any | Any | Clone Operation succeed but node failing join GR when relay logs are present |
103316 | 2021-04-14 11:49 | 2021-04-14 15:55 | MySQL Server: Group Replication | Verified (1080 days) | S6 | 8.0.23 | Any | Any | Group replication assertion / memory corruption |
103421 | 2021-04-22 8:22 | 2021-07-15 8:46 | MySQL Server: Group Replication | Duplicate (988 days) | S2 | CentOS | Any | DDL in group replication cluster also if online cause full stop of write operati | |
104523 | 2021-08-03 14:44 | 2021-11-22 16:14 | MySQL Server: Group Replication | Closed (858 days) | S4 | 8.0.26 | Any | Any | Improve logging of GCS communication issues. |
105436 | 2021-11-03 4:06 | 2022-05-31 14:11 | MySQL Server: Group Replication | Verified (771 days) | S3 | 8.0.28 | Debian | Any | GRepl APPLIER_QUEUE=1 after 8.0.27 upgrade, even on primary node |
108421 | 2022-09-07 21:52 | 2022-09-08 10:00 | MySQL Server: Group Replication | Verified (568 days) | S2 | 8.0.29 | Any | Any | Events remain in SLAVESIDE_DISABLED after a node is promoted to PRIMARY in GR |
108824 | 2022-10-19 10:21 | 2022-10-19 10:52 | MySQL Server: Group Replication | Verified (527 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
110155 | 2023-02-21 14:07 | 2023-02-21 14:22 | MySQL Server: Group Replication | Verified (402 days) | S4 | 8.0.32 | Any | Any | Improve GR error MY-013780 reporting |
111210 | 2023-05-31 6:40 | 2023-05-31 7:01 | MySQL Server: Group Replication | Verified (303 days) | S4 | 8.0 | Any | Any | please add weight to replication_group_members |
112542 | 2023-09-27 16:20 | 2024-01-15 14:20 | MySQL Server: Group Replication | Verified (167 days) | S3 | 8.0.33 | Debian | Any | MySQL GR does not see tables with GIPK if show_gipk is OFF |
113089 | 2023-11-15 13:07 | 2023-12-04 10:40 | MySQL Server: Group Replication | Closed (116 days) | S1 | 8.0.23 | Linux (#84~18.04.1) | x86 | Transaction inconsistency in Group Replication with AFTER mode |
113548 | 2024-01-04 7:38 | 2024-01-09 9:30 | MySQL Server: Group Replication | Duplicate (80 days) | S2 | 8.0.34-26 | Any | Any | Cloning failing in Mysql Group replication |
114072 | 2024-02-20 21:08 | 2024-03-08 16:19 | MySQL Server: Group Replication | Unsupported (21 days) | S3 | 8.0.35-27 | Linux | Any | Group replication slow down existing asynchronous replication |
75939 | 2015-02-17 21:24 | 2015-09-05 1:00 | MySQL Server: Group Replication | No Feedback (3129 days) | S1 | 5.7.5-labs-group-replication | Linux (ubuntu 14.04) | Any | mysql 5.7.5 group replication failed |
78627 | 2015-09-29 16:45 | 2015-10-08 4:50 | MySQL Server: Group Replication | Not a Bug (3095 days) | S1 | 0.5.0-dmr | CentOS (6.4) | Any | Segmentation fault after running START GROUP_REPLICATION on Oracle Linux 6 |
84337 | 2016-12-26 8:50 | 2017-07-11 11:52 | MySQL Server: Group Replication | Closed (2453 days) | S2 | mysql 5.7.17 | Any | Any | Configure mgr with out root user encounter an error |
85026 | 2017-02-16 17:43 | 2019-01-22 14:23 | MySQL Server: Group Replication | Closed (2398 days) | S3 | 8.0.1 | Any | Any | GROUP MEMBERS BECOMES 'UNREACHABLE' WHEN SERVER WITH LOWER VERSION TRIES TO JOIN |
85047 | 2017-02-17 11:03 | 2017-07-17 12:30 | MySQL Server: Group Replication | Closed (2482 days) | S2 | 5.7.18 | Any | Any | Secondaries allows transactions through ASYNC setup into the group |
86359 | 2017-05-17 14:53 | 2017-11-08 10:27 | MySQL Server: Group Replication | Closed (2387 days) | S3 | 5.7.18 | Any | Any | Avoid setting group_replication_force_members in a partition that holds majority |
89194 | 2018-01-11 19:14 | 2018-04-11 16:23 | MySQL Server: Group Replication | Duplicate (2179 days) | S2 | 5.7.20, 8.0.3 | Any | Any | Wrong certification lead to data inconsistency and GR breakage. |
90488 | 2018-04-18 7:02 | 2018-07-11 1:00 | MySQL Server: Group Replication | Can't repeat (2088 days) | S2 | 5.7.21 MySQL Communinity Edition | Ubuntu (16.04) | x86 | mysqld crash on "start group_replication" with bootstrap |
91151 | 2018-06-05 17:12 | 2019-05-06 3:33 | MySQL Server: Group Replication | Verified (2123 days) | S3 | 8.0.11 | Any | Any | Add a Learner/Observer role to leverage it in WAN setup |
91433 | 2018-06-27 8:12 | 2019-01-22 14:14 | MySQL Server: Group Replication | Closed (2031 days) | S3 | 8.0.13-wl11570 | Any | Any | when a member goes to ERROR, other members see it UNREACHABLE |
92454 | 2018-09-17 7:16 | 2018-11-02 14:34 | MySQL Server: Group Replication | Closed (1974 days) | S3 | 8.0.11-commercial | CentOS | Any | [GCS] Error pushing message into group communication engine |
92875 | 2018-10-21 19:37 | 2018-11-25 1:00 | MySQL Server: Group Replication | No Feedback (1952 days) | S2 | 8.0.11 | Debian (9) | Any | Crash after member tries to recover |
93347 | 2018-11-26 14:56 | 2019-07-25 8:30 | MySQL Server: Group Replication | Closed (1858 days) | S3 | 5.7 | Any | Any | VIEW_CHANGE_LOG_EVENT may not be logged on a overloaded primary |
101178 | 2020-10-15 6:55 | 2021-10-29 1:00 | MySQL Server: Group Replication | No Feedback (883 days) | S4 | 8.0.21 | CentOS (7.5.1804) | x86 (Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz) | The variable group_replication_force_members is better to be case insensitive |
101179 | 2020-10-15 6:55 | 2020-10-20 7:53 | MySQL Server: Group Replication | Duplicate (1256 days) | S4 | 8.0.21 | CentOS (7.5.1804) | x86 (Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz) | The variable group_replication_force_members is better to be case insensitive |
102515 | 2021-02-07 11:03 | 2021-03-09 7:36 | MySQL Server: Group Replication | Verified (1144 days) | S2 | 8.0.23 | Any | Any | Group replication member remains ONLINE even when it gets (far) behind |
103808 | 2021-05-26 4:09 | 2021-07-01 1:00 | MySQL Server: Group Replication | No Feedback (1003 days) | S3 | 8.0.22 | CentOS (CentOS Linux release 7.8.2003 (Core)) | x86 | group repl MY-013328: Certification information is too large for transmission |
91057 | 2018-05-29 10:31 | 2018-11-06 17:00 | MySQL Server: Group Replication | Closed (2031 days) | S3 | 5.7.23 | Any | Any | GR recovery can retry infinitely if count is modified to lower value on the fly |
78749 | 2015-10-08 6:25 | 2015-12-03 14:05 | MySQL Server: Group Replication | Closed (3039 days) | S1 | 0.5.0-dmr | Ubuntu (14.04) | Any | Assertion `!flags.finalized' failed with group replication plugin |
108118 | 2022-08-11 12:22 | 2022-08-22 16:47 | MySQL Server: Group Replication | Verified (596 days) | S4 | 8.0.30 | Any | Any | group replication reconfiguration should not require destroying the group |
106032 | 2022-01-04 14:17 | 2022-01-21 6:47 | MySQL Server: Group Replication | Verified (799 days) | S3 | 8.0.27 Community Server | Debian (11.2) | x86 (HyperV) | MySQL uses up ram/swap after short member disconnect within innodb cluster |
90494 | 2018-04-18 12:04 | 2018-11-06 16:57 | MySQL Server: Group Replication | Closed (2058 days) | S3 | 8.0.12 | Any | Any | gr_exit_state_action=ABORT_SERVER is not considered on compatibility checks |
92981 | 2018-10-29 4:33 | 2019-10-14 11:15 | MySQL Server: Group Replication | Not a Bug (1628 days) | S2 | 5.7.22 | Oracle Linux | Any | Potential connection leak in group replication |
106526 | 2022-02-21 14:12 | 2023-12-01 6:54 | MySQL Server: Group Replication | Verified (765 days) | S3 | 8.0.27 | Any | Any | Having a group member rejoining a group stalls writes to the group |
86957 | 2017-07-05 12:49 | 2019-01-22 14:20 | MySQL Server: Group Replication | Closed (2095 days) | S3 | 5.7.20 | Any | Any | SETTING gr_force_members HITS ERROR1231 SOMETIMES WHILE UNBLOCKING THE GROUP |
87834 | 2017-09-22 8:00 | 2019-01-22 14:17 | MySQL Server: Group Replication | Closed (2228 days) | S3 | 5.7.21 | Any | Any | node joins group even though it is not whitelisted on one of the group member |
88304 | 2017-10-31 11:16 | 2018-02-01 14:03 | MySQL Server: Group Replication | Closed (2269 days) | S3 | 8.0.3 | Any | Any | SOMETIMES MEMBERS ENTER IN ERROR STATE AFTER LONG RECOVERY |
89195 | 2018-01-11 19:15 | 2019-07-25 14:45 | MySQL Server: Group Replication | Closed (1709 days) | S2 | 5.7.20, 8.0.3 | Any | Any | Total ordering of transactions is not respected in Group Replication. |
99659 | 2020-05-21 14:49 | 2020-05-28 15:15 | MySQL Server: Group Replication | Not a Bug (1401 days) | S2 | mysql80-server-8.0.19_2 | FreeBSD ( FreeBSD 12.1-RELEASE r354233 GENERIC amd64) | x86 | Group Replication going to ERROR after Regular operation is restored |
100381 | 2020-07-30 15:07 | 2020-10-14 17:19 | MySQL Server: Group Replication | Can't repeat (1262 days) | S2 | 8.0.21 | CentOS (CentOS Linux release 7.7.1908 (Core)) | x86 ( Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz) | Group replication primary got stuck after attempting to rejoin a group member |
87474 | 2017-08-18 11:07 | 2018-05-31 14:47 | MySQL Server: Group Replication | Closed (2223 days) | S3 | 5.7.20 | Any | Any | Slave channels start before group replication starts preventing joins |
89042 | 2017-12-23 6:47 | 2018-05-31 14:53 | MySQL Server: Group Replication | Closed (2227 days) | S2 | 8.0.5 | Any | Any | START GR HANGS AND WITH THAT NO NEW CONNECTION IS ALLOWED ON THAT SERVER |
90986 | 2018-05-23 9:40 | 2018-11-06 16:58 | MySQL Server: Group Replication | Closed (2031 days) | S3 | 5.7.23 | Any | Any | Config issue makes server skips own details in ER_GRP_RPL_MEMBER_CHANGE msg |
91163 | 2018-06-07 1:10 | 2018-06-22 15:31 | MySQL Server: Group Replication | Can't repeat (2107 days) | S1 | 8.0.11 | CentOS (7.4) | Any | MGR member cannnot be joined, which has more executed transactions than present |
89058 | 2017-12-26 12:15 | 2017-12-29 11:25 | MySQL Server: Group Replication | Not a Bug (2282 days) | S3 | 5.7.20 | Linux | Any | Group Replication(MGR) ERROR while executing concurrent DDL and DML |
89954 | 2018-03-08 6:01 | 2018-04-13 3:09 | MySQL Server: Group Replication | Closed (2177 days) | S2 | mysql-community-server-minimal-5.7.20-1. | Oracle Linux (3.10.0-693.11.6.el7.x86_64) | x86 | InnoDB cluster status inconsistent with group replication |
93578 | 2018-12-12 16:15 | 2019-02-05 10:10 | MySQL Server: Group Replication | Closed (1879 days) | S3 | 8.0.13 | Windows (Windows Server 2008 R2 Std) | x86 (64-bit AMD Opteron 6380) | group_replication fatal error, mysqld dies |
96244 | 2019-07-18 7:25 | 2019-12-02 14:28 | MySQL Server: Group Replication | No Feedback (1642 days) | S3 | 8.0.16 | Ubuntu (Ubuntu 18.04 in Digital Ocean) | Any | [GCS] The member was unable to join the group. Local port: 33061 |
97293 | 2019-10-18 16:51 | 2019-11-20 16:46 | MySQL Server: Group Replication | Not a Bug (1591 days) | S2 | at least 8.0.16, 8.0.17 & 8.0.18 | Ubuntu (Ubuntu 18.04.2 LTS) | x86 (GNU/Linux 4.15.0 x86_64) | group replication plugin memory leak |
102433 | 2021-02-01 8:49 | 2021-02-01 14:04 | MySQL Server: Group Replication | Verified (1152 days) | S4 | 8.0 | Any | Any | Lightweigth group replication consensus member without the full database |
104117 | 2021-06-26 2:36 | 2021-06-26 2:39 | MySQL Server: Group Replication | Closed (1007 days) | S2 | mysql8.0.23 mysql8.0.24 | Any | Any | MGR all second node abnormal stop |
113974 | 2024-02-13 9:05 | 2024-02-13 9:26 | MySQL Server: Group Replication | Verified (45 days) | S4 | 8.0 | Any | Any | improve GR error reporting |
89147 | 2018-01-08 22:18 | 2018-01-11 9:52 | MySQL Server: Group Replication | Verified (2269 days) | S4 | 5.7.20,8.0.3 | Any | Any | The field end_log_pos in Group Replication error messages is ambiguous. |
91870 | 2018-08-02 11:33 | 2019-01-22 14:00 | MySQL Server: Group Replication | Closed (1934 days) | S3 | 8.0.13 | Any | Any | ALL MEMBERS ARE EXITED FROM GR WHEN 1/4 NODE TRIED TO REJOIN AFTER network drop |
99778 | 2020-06-04 12:27 | 2020-07-02 14:12 | MySQL Server: Group Replication | Closed (1366 days) | S2 | 8.0.18 | Any | Any | Error when processing certification information in the incremental recovery proc |
100881 | 2020-09-17 18:08 | 2020-09-18 10:44 | MySQL Server: Group Replication | Can't repeat (1288 days) | S2 | 8.0.17 | SUSE (15 SP01) | x86 (x86_64) | [ERROR] [MY-010584] [Repl] Error executing row event: Error_code: MY-001146 |
108417 | 2022-09-07 15:27 | 2022-09-20 11:26 | MySQL Server: Group Replication | Not a Bug (556 days) | S3 | 8.0.30 | Any | Any | Innodb cluster failed after primary removed |
78600 | 2015-09-28 9:44 | 2015-12-11 15:22 | MySQL Server: Group Replication | No Feedback (3031 days) | S1 | 0.5.0-dmr | Ubuntu (14.04) | Any | Compiling group replication plugin will fail because of boost_1_58_0 package |
80241 | 2016-02-02 19:35 | 2016-08-02 19:31 | MySQL Server: Group Replication | Closed (2796 days) | S3 | 0.7.0-labs | CentOS (el7-x86-64bit) | Any | Starting group replication causes MySQL to crash with sig 6 with selinux |
84008 | 2016-11-29 18:24 | 2017-11-08 10:21 | MySQL Server: Group Replication | Closed (2555 days) | S3 | 8.0.1 | Any | Any | GR+MTS: ER1755 can be improved for MTS LC -> MTS DATABASE |
85164 | 2017-02-24 9:31 | 2017-11-08 10:22 | MySQL Server: Group Replication | Closed (2384 days) | S3 | 5.7.18 | Any | Any | GR SHOULD BLOCK OPERATIONS ON NON-COMPLAINT TABLES IN GR+ASYNC SETUP |
86956 | 2017-07-05 12:04 | 2017-08-25 10:48 | MySQL Server: Group Replication | Verified (2458 days) | S3 | 5.7.18 | Any | Any | Joining group timeout on permissions error |
89141 | 2018-01-08 22:07 | 2018-04-11 16:23 | MySQL Server: Group Replication | Duplicate (2179 days) | S2 | 5.7.20,8.0.3 | Any | Any | Error in Group Replication caused by bad Write Set tracking. |
89148 | 2018-01-08 22:23 | 2019-06-04 1:24 | MySQL Server: Group Replication | Verified (2237 days) | S4 | 5.7.20 and 8.0.3 | Any | Any | The timestamp of the GITD events in the GR relay log look wrong. |
89404 | 2018-01-25 11:51 | 2021-06-23 19:40 | MySQL Server: Group Replication | Verified (2254 days) | S4 | 8.0.4 | Any | Any | inconsistent support of CIDR or subnet notation |
90217 | 2018-03-26 15:07 | 2019-01-08 15:13 | MySQL Server: Group Replication | Closed (1907 days) | S1 | 8.0 | Any | Any | Add IPv6 support for Group Replication |
90534 | 2018-04-20 13:58 | 2023-09-12 10:45 | MySQL Server: Group Replication | Can't repeat (199 days) | S1 | 8.0.11, 8.0.12 | MacOS (10.12.6) | x86 | InnoDB Cluster members stop by failed start of Group Replication |
94004 | 2019-01-22 15:37 | 2019-02-19 12:17 | MySQL Server: Group Replication | Closed (1887 days) | S2 | 8.0.14 | Debian (Stretch) | x86 (amd64) | Cannot setup replication without ipv6 since 8.0.14 |
94429 | 2019-02-21 18:00 | 2019-07-25 8:36 | MySQL Server: Group Replication | Closed (1844 days) | S3 | 5.7.26 | Any | Any | MySQL 5.7 lowest member version join check should be with group lowest |
95068 | 2019-04-20 4:22 | 2019-06-26 15:04 | MySQL Server: Group Replication | Closed (1738 days) | S4 | 8.0.15 | Any | Any | Group Replication does not support SSL wildcard certificates |
98524 | 2020-02-09 2:47 | 2023-09-12 10:51 | MySQL Server: Group Replication | Can't repeat (199 days) | S3 | 8.0.19 | CentOS | x86 | ERROR 3096 (HY000): The START GROUP_REPLICATION command failed as there was an e |
100925 | 2020-09-23 9:02 | 2020-09-24 17:49 | MySQL Server: Group Replication | Closed (1282 days) | S2 | 8.0.20, 8.0.21 | Ubuntu | Any | The Mgr parameter does not match the description in the official MySQL document |
102075 | 2020-12-26 9:25 | 2020-12-28 15:01 | MySQL Server: Group Replication | Duplicate (1187 days) | S2 | 5.7.29 | CentOS (CentOS Linux release 7.5.1804 (Core) ) | x86 (Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz) | network and server is ok, but GR node been unreachable |
104646 | 2021-08-17 15:24 | 2021-10-01 1:00 | MySQL Server: Group Replication | No Feedback (911 days) | S2 | 8.0.26 | Debian (10.10) | x86 | InnoDB group replication stalled on large transaction and high network bandwidth |
104677 | 2021-08-20 12:04 | 2021-09-24 1:00 | MySQL Server: Group Replication | No Feedback (918 days) | S3 | 8.0.23 | Debian | Any | Old joiner blocked for a long time in the failure recovery(Local recovery phase) |
106430 | 2022-02-10 8:41 | 2022-02-17 14:31 | MySQL Server: Group Replication | Can't repeat (771 days) | S3 | Any (OKD) | x86 | Timeout on wait for view after joining group | |
107635 | 2022-06-22 14:47 | 2022-07-20 15:43 | MySQL Server: Group Replication | Closed (623 days) | S1 | 8.0.* | Any | Any | event scheduler cause error on group replication |
109580 | 2023-01-11 8:02 | 2023-01-11 15:23 | MySQL Server: Group Replication | Not a Bug (443 days) | S3 | 5.7.40 | Any | Any | Timeout on wait for view after joining group |
109615 | 2023-01-13 7:14 | 2023-01-17 19:05 | MySQL Server: Group Replication | Not a Bug (437 days) | S3 | 5.7.40 | Any | Any | Timeout on wait for view after joining group |
110773 | 2023-04-23 7:56 | 2023-11-28 21:08 | MySQL Server: Group Replication | Verified (127 days) | S3 | mysql 8.0.32 | Any | Any | group_replication start faild use different ips and same port on same server |
112368 | 2023-09-17 14:39 | 2023-09-21 2:29 | MySQL Server: Group Replication | Can't repeat (190 days) | S1 | 5.7.36 | Debian (Debian GNU/Linux 10 (buster)) | Any | Mismatched SQL for the same GTID transaction across primary and secondary |
112967 | 2023-11-06 1:07 | 2023-12-07 1:00 | MySQL Server: Group Replication | No Feedback (114 days) | S2 | 8.0.28 | Debian (Debian GNU/Linux 10 (buster)) | x86 | Crash when a member is immediately reconnected after disconnection |
114263 | 2024-03-07 13:59 | 2024-03-11 10:41 | MySQL Server: Group Replication | Need Feedback (21 days) | S2 | 8.0.31 | Any | Any | Mysql innodb cluster hangs and processes are waiting for handler commit |
112619 | 2023-10-04 15:44 | 2023-10-06 9:45 | MySQL Server: Group Replication | Verified (175 days) | S3 | 8.0.34 | Any | Any | STOP GROUP_REPLICATION on primary during ALTER leads to a confusing message. |
112779 | 2023-10-20 3:57 | 2023-10-24 6:39 | MySQL Server: Group Replication | Can't repeat (157 days) | S3 | 8.0.33 | Any | Any | Not auto rejoin after failing to parse relay log |
108856 | 2022-10-23 15:25 | 2022-10-25 17:04 | MySQL Server: Group Replication | Can't repeat (521 days) | S2 | 8.0.15 | CentOS | x86 | Group replication executes different transactions with same GTID |
110880 | 2023-05-02 3:50 | 2023-05-05 11:57 | MySQL Server: Group Replication | Verified (329 days) | S2 | 8.0.32 | Any | Any | XA COMMIT at before_commit return fail breaks group replication recovery |
109668 | 2023-01-17 21:56 | 2024-01-26 6:08 | MySQL Server: Group Replication | Verified (291 days) | S2 | 8.0.27, 8.0.33 | CentOS | x86 | XCom connection stalled forever in read() syscall over network |
113839 | 2024-01-31 19:30 | 2024-02-03 16:56 | MySQL Server: Group Replication | Verified (57 days) | S3 | 8.0.35 | Any | Any | Cannot elect a new PRIMARY when async connection failover is in use |
112277 | 2023-09-06 15:10 | 2023-09-10 12:34 | MySQL Server: Group Replication | Can't repeat (203 days) | S1 | 5.7.43 | Any | Any | MySQL block forever |
76876 | 2015-04-28 18:53 | 2016-04-27 15:03 | MySQL Server: Group Replication | Closed (3182 days) | S3 | 0.4.0 | Any | Any | --transaction-write-set-extraction is considering non unique and NULL keys |
78619 | 2015-09-29 8:19 | 2016-08-17 3:50 | MySQL Server: Group Replication | Closed (2781 days) | S1 | 0.5.0-dmr | Linux (CentOS 7, Ubuntu 14.04) | Any | There is no input in error log indicating stopped corosync or wrong username |
79499 | 2015-12-03 2:25 | 2015-12-22 12:07 | MySQL Server: Group Replication | Closed (3020 days) | S3 | 0.6 | Any | Any | MySQL crash when xcom of Group Replication assign the same port as that of DB |
75852 | 2015-02-10 20:15 | 2015-05-11 1:00 | MySQL Server: Group Replication | No Feedback (3246 days) | S3 | server:5.7.5-labs-group-replication | Linux | Any | mysql5.7.5 fail to start command-line client |
79564 | 2015-12-09 6:59 | 2016-09-16 11:47 | MySQL Server: Group Replication | Not a Bug (2751 days) | S3 | 0.6, 0.8 | Any | Any | MySQL Group Replication stop replicate on conflict operations |
82385 | 2016-07-30 0:32 | 2016-07-31 3:14 | MySQL Server: Group Replication | Closed (2798 days) | S2 | MySQL 5.7.14 | Linux (CentOS 6.5) | Any | Group Replication Plugin failing when plugin_load |
82481 | 2016-08-06 17:28 | 2016-12-02 13:01 | MySQL Server: Group Replication | Closed (2674 days) | S1 | 5.7.14 | Any | Any | MySQL Group Replication 0.8 is asynchronous |
82584 | 2016-08-15 12:40 | 2016-12-12 10:35 | MySQL Server: Group Replication | Closed (2664 days) | S1 | 5.7.14 | CentOS (7) | Any | task_write: Assertion `con->fd >= 0' failed with group replication |
82687 | 2016-08-23 1:59 | 2017-07-11 11:52 | MySQL Server: Group Replication | Closed (2453 days) | S3 | Any | Any | group replication should not require root@'%' to exist and have privileges | |
84224 | 2016-12-16 7:16 | 2017-01-31 5:04 | MySQL Server: Group Replication | Can't repeat (2614 days) | S3 | 5.7.17-log | Linux (centos 6.6) | Any | mysql group replication bug |
84674 | 2017-01-25 22:05 | 2017-02-16 10:59 | MySQL Server: Group Replication | Closed (2598 days) | S3 | 5.7.latest | Any | Any | Having an unresolvable hostname in group_repl should not block group replication |
82581 | 2016-08-15 10:21 | 2021-11-03 0:08 | MySQL Server: Group Replication | Verified (2636 days) | S1 | 5.7.14 | CentOS (7) | Any | altering table engine from innodb to memory will break group replication |
84731 | 2017-01-31 8:56 | 2017-09-18 10:30 | MySQL Server: Group Replication | Closed (2384 days) | S3 | 5.7.17 | Any | Any | Group Replication: mysql client connections hang during group replication start |
86858 | 2017-06-29 3:19 | 2017-11-08 10:32 | MySQL Server: Group Replication | Closed (2394 days) | S2 | 5.7.18 | Any | Any | Confusing GR error message: check credentials, but issue is hostnanme resolving |
87208 | 2017-07-26 14:05 | 2017-07-31 12:24 | MySQL Server: Group Replication | Not a Bug (2433 days) | S3 | 5.7.18 | Any | Any | Flow control mechanism does not prevent nodes from lagging further behind |
87631 | 2017-08-31 16:06 | 2018-02-01 14:01 | MySQL Server: Group Replication | Closed (2271 days) | S2 | 8.0.3 | Any | Any | LOAD DELAYS SWITCHING A GR NODE FROM RECOVERING TO ONLINE |
88452 | 2017-11-13 1:15 | 2018-02-01 14:03 | MySQL Server: Group Replication | Closed (2298 days) | S2 | 5.7.19 | Any | Any | No Check for duplicatio @@server_uuid when joining group |
88841 | 2017-12-09 15:07 | 2018-05-31 14:52 | MySQL Server: Group Replication | Closed (2257 days) | S3 | 8.0.4 | Any | Any | Typos in 'Initialized group communication with configuration' message |
89059 | 2017-12-26 18:54 | 2018-05-31 14:58 | MySQL Server: Group Replication | Closed (2226 days) | S3 | 8.0.11 | Any | Any | LAST_CONFLICT_FREE_TRANSACTION shows different values in group (empty on joiner) |
89142 | 2018-01-08 22:09 | 2019-04-30 15:41 | MySQL Server: Group Replication | Closed (1795 days) | S4 | 5.7.20, 8.0.3 | Any | Any | Make FLUSH RELAY LOGS work for Group Replication. |
89145 | 2018-01-08 22:15 | 2018-01-11 9:47 | MySQL Server: Group Replication | Verified (2269 days) | S4 | 5.7.20,8.0.3 | Any | Any | Provide relay log details in case of Group Replication applier failure. |
89381 | 2018-01-24 12:53 | 2018-03-08 1:00 | MySQL Server: Group Replication | No Feedback (2214 days) | S2 | 8.0.4 | Debian (9.3) | Any | Rolling upgrading Group Replication using packages |
91150 | 2018-06-05 16:02 | 2018-08-01 0:17 | MySQL Server: Group Replication | Verified (2067 days) | S4 | 8.0.11 | Any | Any | Force primary to stop accept writes on low number of members in the group |
91793 | 2018-07-25 16:25 | 2019-01-22 14:02 | MySQL Server: Group Replication | Closed (1906 days) | S4 | 8.0.12 | Any | Any | Use the new shutdown service when gr_exit_state_action=ABORT_SERVER |
91933 | 2018-08-08 9:22 | 2019-03-12 1:00 | MySQL Server: Group Replication | No Feedback (1845 days) | S1 | 8.0.11 | CentOS | Any | MySQL Group Replication - Transaction hangs in COMMIT state at primary |
92110 | 2018-08-21 18:02 | 2019-07-25 8:27 | MySQL Server: Group Replication | Closed (1845 days) | S3 | 8.0.13 | Any | Any | Errors when joining on start may lead to a stale view of the group |
92293 | 2018-09-05 8:32 | 2018-11-19 16:03 | MySQL Server: Group Replication | Verified (1959 days) | S4 | 5.7, 8.0 | Any | Any | MySQL InnoDB Cluster/Group Replication Server StartUp Sequence Request |
94213 | 2019-02-06 10:31 | 2019-07-25 8:35 | MySQL Server: Group Replication | Closed (1830 days) | S3 | 8.0.14 | Any | Any | group_replication_consistency=AFTER does not include BEFORE_ON_PRIMARY_FAILOVER |
97707 | 2019-11-20 12:39 | 2023-09-12 10:49 | MySQL Server: Group Replication | Can't repeat (199 days) | S1 | all version with MGR | Any | Any | group replication lost transaction when init by ansible |
97836 | 2019-11-30 12:54 | 2023-12-18 5:59 | MySQL Server: Group Replication | Verified (1576 days) | S2 | 8.0.18 | Linux (CentOS Linux release 7.6.1810) | Any (Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz) | In group replication foreign key will break slave aplier |
100221 | 2020-07-14 21:13 | 2020-08-13 1:32 | MySQL Server: Group Replication | Not a Bug (1324 days) | S2 | 8.0 | Ubuntu | x86 | MySQL Group Replication between hosts running containers not working |
102556 | 2021-02-10 15:48 | 2021-04-06 12:18 | MySQL Server: Group Replication | Verified (1088 days) | S2 | 8.0.21 | CentOS (Release: 7.7.1908) | x86 (Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz) | Apparent deadlock involving group replication applier threads |
102742 | 2021-02-25 18:27 | 2021-05-25 16:05 | MySQL Server: Group Replication | Closed (1039 days) | S3 | 8.0.23 | Windows (Windows Server 2019) | x86 | Distributed recovery fails if performed while many rows are being inserted |
105748 | 2021-11-30 11:47 | 2021-12-13 13:07 | MySQL Server: Group Replication | Duplicate (837 days) | S2 | Any | Any | Why is group_replication_consistency = AFTER crashing a Group Replication cluste | |
106815 | 2022-03-24 8:45 | 2024-01-18 7:21 | MySQL Server: Group Replication | Verified (71 days) | S4 | 8.0.28 | Any | Any | improve instrumentation of group replication group changes |
110537 | 2023-03-29 4:02 | 2023-03-31 0:37 | MySQL Server: Group Replication | Can't repeat (364 days) | S1 | 5.7.40 | Any | Any | MySQL cluster fail to auto recover |
112888 | 2023-10-30 21:35 | 2023-10-31 1:42 | MySQL Server: Group Replication | Closed (150 days) | S3 | 8.0.27 | Any | Any | View_change_log_event's in secondary cluster break cross-DC failovers |
113838 | 2024-01-31 19:24 | 2024-02-14 0:27 | MySQL Server: Group Replication | Closed (44 days) | S3 | 8.0+ | Any | Any | Async connection failover prevents failed Group Replication member rejoin |
81109 | 2016-04-17 4:30 | 2016-04-17 5:10 | MySQL Server: Group Replication | Closed (2903 days) | S2 | 5.7.13 | Windows (Windows Server 2012R) | Any | mysqld crash on windows 2012 server when GR cluster have another node in Linux |
81565 | 2016-05-24 8:45 | 2016-05-24 8:48 | MySQL Server: Group Replication | Closed (2866 days) | S3 | Ubuntu (15.10) | Any | 2 of 3 GR nodes down, but replication_group_members reports otherwise | |
83218 | 2016-09-30 7:26 | 2017-04-28 12:58 | MySQL Server: Group Replication | Closed (2569 days) | S2 | 5.7.15-labs, 5.7.17 | Red Hat | Any | DML operations in multiple sessions fail |
84313 | 2016-12-22 9:32 | 2017-06-26 5:02 | MySQL Server: Group Replication | Duplicate (2636 days) | S3 | 5.7.17 | Debian | Any | mysql group replication should not rely on hostnames |
84315 | 2016-12-22 10:51 | 2017-02-17 8:38 | MySQL Server: Group Replication | Verified (2597 days) | S4 | 5.7.17 | Debian | Any | add mysql group replication bootstrap option to init script |
84329 | 2016-12-24 12:31 | 2017-06-09 14:44 | MySQL Server: Group Replication | Closed (2485 days) | S3 | 5.7.17 | Any | Any | Some Class B private address is not permitted automatically |
84574 | 2017-01-20 0:39 | 2017-02-09 12:53 | MySQL Server: Group Replication | Not a Bug (2605 days) | S2 | 5.7.17 | Any | Any | In Group Replication, DDL execute on partitioned node leads to split brain |
84727 | 2017-01-31 8:16 | 2017-06-26 15:59 | MySQL Server: Group Replication | Closed (2468 days) | S2 | 5.7.17 | Any | Any | GR: Partitioned Node Should Get Updated Status and not accept writes |
84773 | 2017-02-01 14:29 | 2017-10-04 14:14 | MySQL Server: Group Replication | Closed (2368 days) | S5 | 5.7.17 | Linux | Any | Flow control slows down throughput while a node join the cluster |
84774 | 2017-02-01 14:53 | 2022-09-13 17:20 | MySQL Server: Group Replication | Verified (2612 days) | S5 | 5.7.17 | Any | Any | Performance drop every 60 seconds |
84792 | 2017-02-02 12:49 | 2017-05-03 13:18 | MySQL Server: Group Replication | Can't repeat (2522 days) | S3 | 5.7.17 | Any | Any | Idle GR Cluster: Member CPU hog |
85667 | 2017-03-28 9:47 | 2017-07-17 12:31 | MySQL Server: Group Replication | Closed (2466 days) | S3 | 5.7.18 | Any | Any | GR node is in RECOVERING state if binlog_checksum configured on running server |
85781 | 2017-04-04 12:32 | 2017-11-08 10:23 | MySQL Server: Group Replication | Closed (2384 days) | S3 | 5.7.19 | Any | Any | GR ALLOWS OPERATIONS ON NON-COMPLAINT TABLES THROUGH MYSQLBINLOG |
86142 | 2017-04-30 19:06 | 2017-10-13 17:58 | MySQL Server: Group Replication | Closed (2359 days) | S3 | 5.7.19 | Any | Any | GR+XA: Assert `! is_set() at sql_error.cc:406 when member is in ERROR/RECOVERING |
86149 | 2017-05-01 17:00 | 2022-01-21 2:55 | MySQL Server: Group Replication | No Feedback (2493 days) | S3 | 5.7.17 | CentOS | Any | MySQL Group Replication Crash - Failing assertion: !cursor->index->is_committed |
86222 | 2017-05-08 17:07 | 2017-11-08 10:24 | MySQL Server: Group Replication | Closed (2387 days) | S3 | 5.7.17 | Any | Any | GR Member stop must all asynchronous channels that are feeding data into it |
86271 | 2017-05-10 14:42 | 2017-11-08 10:24 | MySQL Server: Group Replication | Closed (2387 days) | S3 | 8.0.2 | Any | Any | The delayed plugin initialization thread is left running when it is not needed |
86626 | 2017-06-08 16:42 | 2017-11-08 10:28 | MySQL Server: Group Replication | Closed (2384 days) | S3 | 5.7.19 | Any | Any | Group replication partition handling thread is not instrumented on perf schema |
86669 | 2017-06-13 4:47 | 2017-11-08 10:31 | MySQL Server: Group Replication | Closed (2384 days) | S3 | 8.0.2 | Any | Any | GR overrides auto_increment_increment=1 and auto_increment_offset=1 |
86874 | 2017-06-29 16:44 | 2018-02-01 14:01 | MySQL Server: Group Replication | Closed (2271 days) | S3 | 5.7.19 | Any | Any | Group Replication variable updates are not safe against stop |
87206 | 2017-07-26 13:22 | 2017-11-08 10:32 | MySQL Server: Group Replication | Closed (2387 days) | S3 | 8.0.3 | Any | Any | flow control variables are not validated passed as cmd line during server start |
87235 | 2017-07-28 7:33 | 2017-09-26 14:23 | MySQL Server: Group Replication | Can't repeat (2376 days) | S2 | 5.7.19 | CentOS (Linux localhost 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86) | Any | "STOP GROUP_REPLICATION" cause deadlock |
87759 | 2017-09-14 15:16 | 2018-04-12 5:23 | MySQL Server: Group Replication | Closed (2297 days) | S3 | 8.0.4 | Any | Any | Assert `server_engine_initialized()' at delayed_plugin_initialization.cc:167 |
88163 | 2017-10-20 7:03 | 2018-04-12 5:22 | MySQL Server: Group Replication | Duplicate (2178 days) | S3 | 5.7.20 | Debian (Debian 8) | Any | /usr/sbin/mysqld --initialize-insecure hang with group replication enabled |
88329 | 2017-11-02 10:40 | 2018-05-31 14:48 | MySQL Server: Group Replication | Closed (2227 days) | S3 | 8.0.3 | Any | Any | Group replication thread's initialization methods can get stuck waiting |
88597 | 2017-11-22 5:05 | 2017-11-23 7:35 | MySQL Server: Group Replication | Not a Bug (2319 days) | S3 | 5.7 | Any | Any | Plugins that happen to be called group_replication cant be uninstalled anymore? |
88602 | 2017-11-22 9:18 | 2018-05-31 14:49 | MySQL Server: Group Replication | Closed (2228 days) | S2 | 9.0.0 | Any | Any | Assert `! is_set()' at sql_error.cc:402 if set var executed on S2 post S1 killed |
88697 | 2017-11-29 12:12 | 2018-05-31 14:50 | MySQL Server: Group Replication | Closed (2293 days) | S3 | 5.7.22 | Any | Any | Group replication channel observers may use null pointers on uninstall |
88944 | 2017-12-15 21:31 | 2018-05-31 14:57 | MySQL Server: Group Replication | Closed (2223 days) | S2 | 8.0.4 | Any | Any | Server freeze on failed auto-rejoin |
89146 | 2018-01-08 22:16 | 2018-06-20 16:45 | MySQL Server: Group Replication | Closed (2109 days) | S3 | 5.7.20, 8.0.3 | Any | Any | Binlog name and Pos are wrong in group_replication_applier channel's error msgs |
90146 | 2018-03-20 18:57 | 2018-11-06 16:56 | MySQL Server: Group Replication | Closed (2108 days) | S3 | 8.0.11 | Any | Any | If GNO exhausts GR hits with Assert `!executed_gtids.contains_gtid(gtid)' |
90284 | 2018-04-03 1:05 | 2018-04-03 14:50 | MySQL Server: Group Replication | Verified (2187 days) | S4 | Any | Any | Add an acceptor only role to leverage it in single-primary mode | |
90461 | 2018-04-17 4:58 | 2018-11-22 10:19 | MySQL Server: Group Replication | Closed (1960 days) | S4 | 8.0.4 | Any | Any | Change group_replication_single_primary_mode online |
90483 | 2018-04-17 23:54 | 2018-08-07 8:57 | MySQL Server: Group Replication | Closed (2061 days) | S3 | 5.7.21, 8.0.4 | CentOS | Any | dns based seeds resolving to itself causes GR to not start |
91147 | 2018-06-05 15:21 | 2018-10-29 13:50 | MySQL Server: Group Replication | Closed (1982 days) | S4 | 8.0.11 | Any | Any | Force primary member to give up its role |
91356 | 2018-06-21 11:51 | 2018-07-09 7:58 | MySQL Server: Group Replication | Not a Bug (2090 days) | S3 | 8.0.11 | Any | Any | Member state is Recovering, but group_replication_recovery thread is not running |
91537 | 2018-07-03 12:45 | 2019-01-22 14:10 | MySQL Server: Group Replication | Closed (1925 days) | S3 | 8.0.13 | Any | Any | Executing GROUP_ACTION should be blocked WHEN THERE ARE UNREACHABLE members |
91658 | 2018-07-16 9:30 | 2018-10-17 22:24 | MySQL Server: Group Replication | Closed (2083 days) | S3 | 5.7.22 | CentOS | Any | Kubernetes&MGR Executing "start group_replication" fails |
91660 | 2018-07-16 9:58 | 2018-07-23 11:42 | MySQL Server: Group Replication | Unsupported (2076 days) | S3 | 5.7.22 | CentOS | Any | Kubernetes&MGR Executing "start group_replication" fails |
91722 | 2018-07-20 3:08 | 2018-11-01 8:40 | MySQL Server: Group Replication | Verified (2054 days) | S1 | 5.7.22 | Any | Any | MGR may becomes a one-member-online system but still provide service |
92686 | 2018-10-05 12:46 | 2019-01-17 16:22 | MySQL Server: Group Replication | Not a Bug (1898 days) | S2 | 8.0.12 | Any | Any | Mysql server 8.0.12 group replication |
92690 | 2018-10-05 14:18 | 2019-02-25 13:28 | MySQL Server: Group Replication | Closed (1859 days) | S2 | 5.7.23, 8.0.12 | Any | Any | Group Replication split brain with faulty network |
92829 | 2018-10-17 14:32 | 2019-01-22 13:52 | MySQL Server: Group Replication | Closed (1934 days) | S3 | 8.0.14 | Any | Any | Verify coordinated action safety agains plugin starts and stops |
93130 | 2018-11-08 18:58 | 2019-01-22 13:54 | MySQL Server: Group Replication | Closed (1949 days) | S3 | 5.7.25 | Any | Any | Backport Bug#28443958 to mysql-5.7 |
93598 | 2018-12-13 17:10 | 2019-07-25 8:33 | MySQL Server: Group Replication | Closed (1862 days) | S3 | 5.7.26 | Any | Any | Remove GR plugin README file |
96158 | 2019-07-10 12:32 | 2020-01-20 9:54 | MySQL Server: Group Replication | Closed (1716 days) | S2 | 8.0.18 | Any | Any | default_table_encryption can be changed on running member via SET PERSIST |
96213 | 2019-07-16 6:01 | 2019-11-26 5:14 | MySQL Server: Group Replication | No Feedback (1667 days) | S3 | Any | Any | group replication auto_increment_offset is not accurate | |
96606 | 2019-08-21 16:58 | 2019-10-30 12:36 | MySQL Server: Group Replication | Closed (1612 days) | S4 | 8.0 | Any | Any | InnoDB Cluster - Prevents reads on Failed Primary Node |
96987 | 2019-09-24 7:36 | 2019-10-15 14:07 | MySQL Server: Group Replication | Verified (1627 days) | S4 | 5.7.22;8.0.11 | Any | Any | MySQL Group Replication task scheduling optimization |
98239 | 2020-01-15 13:49 | 2020-02-28 11:39 | MySQL Server: Group Replication | Not a Bug (1491 days) | S3 | 8.0.19 | Ubuntu (ubuntu 1804 desktop x64) | Any | member state error when alter column while other member commit transaction later |
98643 | 2020-02-18 8:11 | 2020-05-12 15:07 | MySQL Server: Group Replication | Closed (1417 days) | S3 | 8.0.18 | Any | Any | group replication will be block primary node shutdown |
99133 | 2020-03-31 15:08 | 2024-01-30 17:50 | MySQL Server: Group Replication | Verified (1452 days) | S3 | 8.0.19 | Any | Any | Group Replication Performance Degradation with partial network outage |
99745 | 2020-05-29 16:13 | 2021-07-13 5:30 | MySQL Server: Group Replication | No Feedback (1365 days) | S3 | 8.0.16 | Ubuntu (18.04) | x86 | Slave stops with HA_ERR_KEY_NOT_FOUND error |
100103 | 2020-07-03 13:17 | 2020-08-07 1:00 | MySQL Server: Group Replication | No Feedback (1330 days) | S1 | 8.0.11 | Linux (CentOS) | Any | Slave SQL for channel 'group_replication_recovery': Could not execute Write_rows |
101114 | 2020-10-10 6:46 | 2020-11-15 1:00 | MySQL Server: Group Replication | No Feedback (1231 days) | S2 | 8.0.18 | Any | Any | MySQL group replication not set read_only before it joins the GR cluster |
102249 | 2021-01-14 15:56 | 2021-01-27 17:40 | MySQL Server: Group Replication | Verified (1166 days) | S3 | 8.0.22 | Any | Any | Slow query log filling up with performance_schema queries |
105877 | 2021-12-13 12:05 | 2021-12-24 12:45 | MySQL Server: Group Replication | Verified (826 days) | S3 | Red Hat | Any | group replication node always in offline mode after switch | |
106183 | 2022-01-17 12:10 | 2022-01-20 16:56 | MySQL Server: Group Replication | Verified (799 days) | S3 | 8.0.27 | Any | Any | Error when initializing the group communication layer |
107176 | 2022-05-02 10:24 | 2022-06-20 3:55 | MySQL Server: Group Replication | No Feedback (649 days) | S2 | 8.0.28 | Ubuntu (20.04 LTS) | Any | Dual stack ubuntu group replication setup fails on add instance |
107254 | 2022-05-10 12:29 | 2022-05-10 12:45 | MySQL Server: Group Replication | Duplicate (689 days) | S1 | MySQL 8.0.xx | Linux (Centos 7/8) | Any | MySQL Group Replication slave applier breaks due to parallel replication |
107575 | 2022-06-16 5:49 | 2022-06-16 6:20 | MySQL Server: Group Replication | Verified (652 days) | S4 | 8.0.28 | Any | Any | Group replication should pick node with no delay when electing new primary |
28977 | 2007-06-08 14:35 | 2007-06-08 14:46 | MySQL Server: General | Not a Bug (6139 days) | S2 | 5.0.37, 5.0.22 | Any | Any | cannot change the group mysqld runs as |
28449 | 2007-05-15 15:50 | 2007-06-14 19:26 | MySQL Server: General | Closed (6133 days) | S2 | 5.0, 5.1.19 | Any | Any | Server crashes on closing a temporary table after SELECT ... GROUP BY |
33417 | 2007-12-20 19:38 | 2011-02-16 23:43 | MySQL Server: General | No Feedback (5255 days) | S3 | 5.0.46, 5.0.52 | Windows | Any | group by 3 columns with MAX() produces incorrect results |
40275 | 2008-10-23 5:13 | 2015-03-15 20:45 | MySQL Server: General | No Feedback (5605 days) | S3 | 5.0.51a, 5.0.67 | Linux | Any | My SQL Query Problem |
41823 | 2009-01-02 2:13 | 2009-01-02 21:15 | MySQL Server: General | Not a Bug (5565 days) | S2 | 5.0.45 | Linux (Centos) | Any | Order By fails to sort aliased fields containing spaces |
42975 | 2009-02-18 16:07 | 2011-02-16 23:43 | MySQL Server: General | Duplicate (5517 days) | S2 | 5.1.30 | Linux | Any | MySQL Crash: glibc detected double free or corruption |
43914 | 2009-03-27 15:30 | 2011-02-16 23:43 | MySQL Server: General | Closed (5478 days) | S4 | Any | Any | delayed-file param / a function to execute group of statements in another thread | |
48762 | 2009-11-13 14:46 | 2011-02-16 23:44 | MySQL Server: General | No Feedback (5220 days) | S2 | 5.1.40 | Any (Tested on OSx and Vista64) | Any | Having clause does not limit resultset correctly without group by being used |
50945 | 2010-02-05 14:41 | 2010-02-05 14:58 | MySQL Server: General | Not a Bug (5166 days) | S2 | 5.0.20-nt | Windows | Any | I need to group the values in comma separated |
54751 | 2010-06-23 18:56 | 2010-06-29 19:13 | MySQL Server: General | Not a Bug (5022 days) | S3 | 5.1.45 | Any | Any | session variables are evaluated differently in 5.1.24 and 5.1.41/45 in group by |
24931 | 2006-12-09 4:09 | 2006-12-10 14:53 | MySQL Server: General | Duplicate (6319 days) | S1 | 14.7 Distrib 4.1.14, for pc-l | Linux (RH Linux) | Any | count(*) messed up |
28936 | 2007-06-07 0:33 | 2007-06-07 7:51 | MySQL Server: General | Can't repeat (6140 days) | S1 | 5.0.41-Max | Linux | Any | Group by returning incorrect values when sub-query is involved |
29729 | 2007-07-11 18:06 | 2007-07-23 0:44 | MySQL Server: General | Closed (6094 days) | S2 | 5.0.44, 5.0.45 | Linux | Any | datetime compared with date failing to add zero time on group by query |
30439 | 2007-08-15 14:45 | 2007-08-16 5:14 | MySQL Server: General | Duplicate (6070 days) | S3 | 5.0.45 | Linux | Any | tmpdir is not followed for temporary tables in group by |
31035 | 2007-09-14 20:47 | 2007-10-23 0:26 | MySQL Server: General | Closed (6002 days) | S1 | 5.0.50, 5.1.23 | Any | Any | select from function, group by result crasher |
32202 | 2007-11-08 22:30 | 2007-11-19 4:31 | MySQL Server: General | Closed (5975 days) | S2 | 5.0.50 | Any | Any | ORDER BY not working with GROUP BY |
32558 | 2007-11-21 6:46 | 2007-12-12 19:43 | MySQL Server: General | Closed (5952 days) | S1 | 5.1.23 | Any | Any | group by null-returning expression with rollup causes crash |
33771 | 2008-01-09 14:43 | 2008-04-26 3:28 | MySQL Server: General | Closed (5816 days) | S2 | 6.0 BK | Linux (Fedora 8) | Any | -mysqld=--thread-handling=pool-of-threads causes the tests to fail |
35181 | 2008-03-10 12:52 | 2008-03-19 13:36 | MySQL Server: General | Duplicate (5854 days) | S2 | 5.0.51 | Linux (RHEL 5) | Any | MySQL 5.0.51 and 51a are severely broken when a GROUP BY and ORDER BY are applie |
12866 | 2005-08-30 3:11 | 2022-12-04 20:45 | MySQL Server: General | Verified (5280 days) | S4 | 5.0.11 | Windows (Windows 2003 server) | Any | No accessible transaction id within triggers |
42567 | 2009-02-03 12:39 | 2011-02-16 23:43 | MySQL Server: General | Closed (5490 days) | S2 | 5.1.30-community-log | Windows (2003) | Any | Invalid GROUP BY error |
53712 | 2010-05-17 16:13 | 2011-02-16 23:44 | MySQL Server: General | No Feedback (5033 days) | S2 | 5.1.46 | Solaris | Any | ORDER BY causes incorrect query result |
60808 | 2011-04-08 15:06 | 2011-04-08 16:35 | MySQL Server: General | Duplicate (4739 days) | S2 | 5.5.11, 5.1.54, 5.1.41 | Any (win7 64bit, ubuntu 10.04 64 bit) | Any | Duplicate entry for key 'group_key'; Can't write, duplicate key in table |
63609 | 2011-12-05 17:18 | 2011-12-12 18:25 | MySQL Server: General | Duplicate (4491 days) | S3 | Distrib 5.5.17, for FreeBSD7.4 (amd64) | FreeBSD (not tested on other OS) | Any | Query with GROUP by , ORDER BY and LIMIT return one row , not expected count |
26830 | 2007-03-04 5:43 | 2007-03-15 3:00 | MySQL Server: General | Closed (6224 days) | S1 | 5.0.38BK, 5.1.17BK | Any (*) | Any | subquery, group by .. with rollup crashes server |
29438 | 2007-06-29 3:36 | 2007-07-29 8:21 | MySQL Server: General | No Feedback (6088 days) | S3 | 5.0.41 | Any | Any | rollup with multiple "group by" column repeats last grouping column final rollup |
29606 | 2007-07-06 18:57 | 2009-07-20 9:44 | MySQL Server: General | Not a Bug (5366 days) | S4 | 5.1 | Any | Any | LAST ENTRY of a GROUP BY sql statement |
29975 | 2007-07-23 9:51 | 2007-07-23 10:52 | MySQL Server: General | Not a Bug (6094 days) | S3 | 5.0.37 | Linux (Fedora 7.9 (dev)) | Any | TIME_TO_SEC does never return more than 3020399 (838:59:59) |
30109 | 2007-07-27 23:29 | 2007-07-30 14:37 | MySQL Server: General | Not a Bug (6087 days) | S2 | 4.1.20,4.1.23 - 5.0 | Linux | Any | Ambiguous ORDER BY behavior change |
20630 | 2006-06-22 15:45 | 2011-02-16 23:43 | MySQL Server: General | Verified (6490 days) | S4 | 5.0.22 (+?) | Any (all) | Any | Remove restriction on option file parameters being first |
22405 | 2006-09-15 19:39 | 2006-09-18 18:13 | MySQL Server: General | Closed (6402 days) | S1 | 5.1.12 | Linux (Linux) | Any | innodb_mysql.test fail on wrong result file |
22831 | 2006-09-29 16:23 | 2008-10-04 23:12 | MySQL Server: General | Won't fix (5655 days) | S4 | 5.0.24a | Linux (opensuse 10.0) | Any | make the global mode take effect immediately |
24657 | 2006-11-28 15:12 | 2012-05-18 20:19 | MySQL Server: General | Duplicate (5923 days) | S3 | 4.1.22, 5.0.27/4.1BK/5.0BK/5.1BK | FreeBSD (freebsd/Suse Linux 10) | Any | debug assertation fails (string store) |
27023 | 2007-03-10 14:38 | 2015-04-08 2:31 | MySQL Server: General | Can't repeat (5551 days) | S2 | 5.0.32-Debian_3-log, 5.0.67 | Linux (Linux) | Any | out of memory error with COUNT(DISTINCT IF(...)) |
27118 | 2007-03-14 8:36 | 2007-03-26 12:30 | MySQL Server: General | Not a Bug (6213 days) | S2 | 5.033, 5.1 BK, 5.2-falcon | Windows (Windows XP Pro, Linux) | Any | Query doesnt return the same results each and every time |
27119 | 2007-03-14 8:41 | 2007-05-27 9:38 | MySQL Server: General | Closed (6151 days) | S1 | 5.0.38BK | Windows (windows) | Any | server crash with integer division by zero during filesort on huge result |
27147 | 2007-03-14 18:31 | 2007-04-15 16:24 | MySQL Server: General | No Feedback (6193 days) | S3 | 5.0.32-Dotdeb_1.dotdeb.1-log | Linux (Linux - x86_64 - Debian Sarge) | Any | Crash on Query |
27386 | 2007-03-22 23:25 | 2007-07-09 8:59 | MySQL Server: General | Not a Bug (6108 days) | S1 | 5.1.17 Beta | Any (Unknown(ISP) and Mac OS X) | Any | Queries are Returning Results Which are not Ordered |
27643 | 2007-04-04 12:13 | 2007-06-19 0:44 | MySQL Server: General | Closed (6128 days) | S2 | 5.0BK | Any | Any | query failed : 1114 (The table '' is full) |
27849 | 2007-04-16 12:21 | 2011-02-16 23:43 | MySQL Server: General | Verified (6190 days) | S4 | 5.0.37 | Linux | Any | version incompatibility for comma operator between 4.1.x and 5.0.x |
28281 | 2007-05-07 14:13 | 2007-06-19 13:46 | MySQL Server: General | Not a Bug (6128 days) | S2 | 5.0.44-BK, 5.0.37 (Community) | Windows (XP) | Any | GROUP BY returning recs in wrong order |
28494 | 2007-05-17 8:48 | 2007-06-19 1:12 | MySQL Server: General | Closed (6128 days) | S3 | 5.0.41, 5.1 | Linux | Any | Assigning to variable in SELECT spoils result of GROUP BY |
28694 | 2007-05-25 21:50 | 2007-06-26 0:39 | MySQL Server: General | No Feedback (6121 days) | S2 | 5.0.27 | Linux | Any | multiple WHERE exclusions (<>) with many records and exclusions ignored |
29685 | 2007-07-10 9:40 | 2007-07-10 11:38 | MySQL Server: General | Closed (6107 days) | S2 | >=5.0.40 | Any | Any | SELECT with EXISTS and GROUP BY gives wrong result |
29918 | 2007-07-19 22:24 | 2007-07-19 23:37 | MySQL Server: General | Not a Bug (6098 days) | S3 | 5.0.44 | Linux (Gentoo) | Any | Assigning a variable in some SELECT queries yields invalid resuls |
30287 | 2007-08-07 21:49 | 2010-01-13 19:27 | MySQL Server: General | Closed (6061 days) | S2 | 5.0.44, 5.1, 5.0 BK | Linux (x86,x86_64) | Any | tmpdir not respected on GROUP BY |
30874 | 2007-09-06 18:12 | 2007-09-07 14:58 | MySQL Server: General | Can't repeat (6048 days) | S3 | 5.0.26 | Linux | Any | rollup doesn't work with substr |
31095 | 2007-09-19 12:22 | 2007-11-09 0:24 | MySQL Server: General | Closed (5985 days) | S1 | 5.0.48, 5.1.23BK | Any | Any | server crashes with group by null with rollup |
31144 | 2007-09-22 13:34 | 2007-11-16 9:47 | MySQL Server: General | Closed (5978 days) | S2 | 5.1.23, 6.0.3 | Any | Any | crash when subquery within order by/group by clause returns spatial datatype |
31899 | 2007-10-28 19:55 | 2007-10-29 11:19 | MySQL Server: General | Not a Bug (5996 days) | S3 | 5.0.45 | Any | Any | Group functions not working properly when joining tables |
32431 | 2007-11-16 9:57 | 2008-04-20 9:58 | MySQL Server: General | No Feedback (5822 days) | S2 | 5.0.22, 5.0.45 | Linux (2.6.18-8.1.15.el5 x86_64) | Any | MySQLd crashes after double free or corruption error |
33876 | 2008-01-15 17:14 | 2008-02-15 17:47 | MySQL Server: General | No Feedback (5887 days) | S3 | 4.1.16 | Any (Not return correct result) | Any | Query run OK in Mysql 5.0.27 but not run at 4.1.16 |
34382 | 2008-02-07 14:55 | 2008-03-07 15:05 | MySQL Server: General | No Feedback (5866 days) | S3 | 5.0.32 | Any (Sorry none) | Any | Error when using ON DUPLICATE KEY UPDATE table1.field1 = table2.field1,.... |
35090 | 2008-03-05 20:15 | 2011-02-16 23:43 | MySQL Server: General | Verified (5505 days) | S3 | 5.0, 5.1, 6.0 BK | Any (Unix-only?) | Any | umask applied as bitmap instead of as a mask |
36514 | 2008-05-05 18:46 | 2024-02-04 20:45 | MySQL Server: General | Verified (5189 days) | S3 | 5.0 | MacOS (10.5.2) | Any | mysqld_safe gives chown: 'Operation not permitted' for error log on OSX |
31825 | 2007-10-24 20:35 | 2007-10-25 17:13 | MySQL Server: General | Can't repeat (6000 days) | S2 | 5.0.41 | Windows (Not tested on other OS'es) | Any | GROUP BY problem |
34347 | 2008-02-06 12:29 | 2008-02-06 13:27 | MySQL Server: General | Can't repeat (5896 days) | S2 | 5.0.51 | Linux (Debian AMD64) | Any | ORDER BY fails if result is grouped with GROUP BY |
36511 | 2008-05-05 16:09 | 2008-05-05 16:41 | MySQL Server: General | Not a Bug (5807 days) | S2 | 5.0.51 | Any | Any | MySQL allows fields in SELECT list that are not in the GROUP BY statement |
53144 | 2010-04-25 17:09 | 2010-04-25 17:29 | MySQL Server: General | Not a Bug (5087 days) | S3 | 5.0.88 | Any | Any | GROUP BY with ROLLUP includes previous data in rollup |
55892 | 2010-08-10 19:04 | 2010-08-10 21:40 | MySQL Server: General | Not a Bug (4980 days) | S3 | Ver 14.14 Distrib 5.1.38, for Win32 | Windows (windows 7 x64) | Any | parser is too permissive for query - accepts invalid as valid |
56600 | 2010-09-06 17:41 | 2011-02-16 23:44 | MySQL Server: General | Closed (4953 days) | S1 | 5.0.77 | Linux (CentOS VPS OpenVZ) | Any | apache segmentation fault (11) inserting columns with more than 10.000 caracters |
58325 | 2010-11-19 15:00 | 2010-11-23 17:39 | MySQL Server: General | Not a Bug (4875 days) | S3 | 5.0.44, 5.0.91 | Any | Any | group_concat function returns binary result for non-string columns |
58647 | 2010-12-02 5:58 | 2011-02-16 23:44 | MySQL Server: General | No Feedback (4835 days) | S1 | 5.1.47 | Linux (Red Hat Enterprise Linux Server release 5.3 (Tikanga)) | Any | Mysql Crach while killing query |
59192 | 2010-12-28 12:38 | 2010-12-28 14:40 | MySQL Server: General | Not a Bug (4840 days) | S3 | 5.0.81-community | Linux | Any | View not return data |
65300 | 2012-05-13 4:51 | 2012-06-14 1:00 | MySQL Server: General | No Feedback (4307 days) | S2 | 5.5.20 | Windows | Any | doing mysql insert into a database record after 160 records it hangs |
67503 | 2012-11-07 15:48 | 2012-11-08 0:56 | MySQL Server: General | Closed (4159 days) | S2 | 5.5.27 | Linux (CentOS 5.7) | Any | having max(valus) can not return records which valus between {1, -1} |
114475 | 2024-03-25 15:24 | 2024-03-28 11:41 | MySQL Server: General | Not a Bug (3 days) | S3 | 8.0.35 | Windows (11) | x86 (32GB) | COUNT(1) vs SUM of partial counts |
36189 | 2008-04-17 22:44 | 2008-07-09 20:24 | MySQL Server: General | Can't repeat (5742 days) | S3 | 5.0.51a | Linux (RHES 4 and RHES 5) | Any | Order by is not being evaluated when a group by exists on the primary key |
36821 | 2008-05-20 16:25 | 2013-06-18 9:40 | MySQL Server: General | Can't repeat (3937 days) | S3 | 5.0.51a/5.1/6.0 | Linux (Redhat Linux Enterprise 4ES X86_64) | Any | HAVING clause returning different result |
36868 | 2008-05-22 1:17 | 2008-05-23 18:30 | MySQL Server: General | Not a Bug (5789 days) | S2 | 5.051b-community-nt | Windows | Any | UNIQUE contraint reports violation when with VARCHAR field |
38345 | 2008-07-24 12:31 | 2008-07-25 18:13 | MySQL Server: General | Can't repeat (5726 days) | S3 | 5.0.44-log mysql-5.0.44 | Linux (Gentoo Linux) | Any | Result in first column depends on last field in select statments |
41999 | 2009-01-09 15:30 | 2022-09-04 20:45 | MySQL Server: General | Duplicate (5491 days) | S1 | 5.0.67, 5.0.74, 5.1.30 | Linux | Any | SHOW CREATE VIEW returns invalid SQL if subquery is used in SELECT list |
51745 | 2010-03-05 4:29 | 2010-03-05 4:34 | MySQL Server: General | Not a Bug (5138 days) | S2 | Community 5.1 | Any | Any | Lack of GROUP BY fails to stop query execution with non-aggregated column |
62064 | 2011-08-02 22:41 | 2011-08-03 22:35 | MySQL Server: General | Closed (4622 days) | S1 | 5.5.11-log | Linux | Any | Embedded group by query with CURSOR_TYPE_READ_ONLY crashes the server |
78383 | 2015-09-09 14:51 | 2015-09-10 14:28 | MySQL Server: General | Not a Bug (3123 days) | S3 | 5.5 / 5.6 | Any | Any | Bug with group by & group_concat |
53743 | 2010-05-18 10:11 | 2012-05-18 20:19 | MySQL Server: GIS | Open | S4 | Any | Any | Any | union, intersection functions to work on multiple geometries |
81411 | 2016-05-13 4:18 | 2018-09-25 22:04 | MySQL Server: GIS | Closed (2325 days) | S6 | 5.5.49 | Any | Any | Assertion `n_linear_rings > 0' failed. in Gis_polygon::centroid_xy |
83737 | 2016-11-08 9:10 | 2017-12-07 4:07 | MySQL Server: GIS | Closed (2304 days) | S1 | 5.6.34,5.6.38 | Any | Any | Assertion `t1->result_range' failed. |
84834 | 2017-02-06 10:43 | 2018-10-01 16:17 | MySQL Server: GIS | Duplicate (2355 days) | S6 | 5.6.35 | Any | Any | handle_fatal_signal (sig=11) in Gcalc_operation_reducer::get_result_thread |
85070 | 2017-02-20 6:09 | 2017-02-20 6:40 | MySQL Server: GIS | Duplicate (2594 days) | S1 | 5.6.35 | Any | Any | handle_fatal_signal (sig=11) in Gcalc_operation_reducer::free_result |
88801 | 2017-12-07 4:01 | 2018-09-25 22:07 | MySQL Server: GIS | Closed (2236 days) | S6 | 5.6.38 | Any | Any | Assertion `t1->result_range' failed. |
28300 | 2007-05-08 10:03 | 2011-02-16 23:43 | MySQL Server: GIS | Verified (6170 days) | S4 | any | Any | Any | General RTREE indicies |
59111 | 2010-12-22 10:40 | 2011-02-16 23:44 | MySQL Server: GIS | Closed (4797 days) | S3 | 5.6+ | Any | Any | gis crashes when server is compiled without performance schema |
64436 | 2012-02-23 17:00 | 2012-02-23 19:52 | MySQL Server: Information schema | Closed (4418 days) | S3 | 5.5.14-55 | Linux | Any | No results for creation/insertion of a select based on the information schema |
38837 | 2008-08-17 4:01 | 2011-02-16 23:43 | MySQL Server: Information schema | Verified | S3 | 5.0+ | Any | Any | need a way to disable information_schema for security |
38984 | 2008-08-23 18:53 | 2011-11-26 12:29 | MySQL Server: Information schema | Can't repeat (4507 days) | S1 | 6.0, 5.5.4-m3 | Any | Any | Crash in Field_varstring::sql_type at field.cc:7049 |
39646 | 2008-09-25 9:08 | 2008-09-25 9:18 | MySQL Server: Information schema | Not a Bug (5664 days) | S3 | 5.1.26 | Linux | Any | To check space occupied by tables |
43834 | 2009-03-24 15:19 | 2011-02-16 23:43 | MySQL Server: Information schema | Closed (5369 days) | S1 | 6.0-bzr,5.4 | Linux | Any | Assertion in Natural_join_column::db_name() on an I_S query |
22887 | 2006-10-02 11:55 | 2006-12-07 12:57 | MySQL Server: Information schema | No Feedback (6322 days) | S3 | 5.1.11 | Linux (ubuntu dapper drake linux) | Any | information_schema.FILES.TABLESPACE_NAME not null for UNDOFILEs |
26289 | 2007-02-12 15:05 | 2007-02-13 10:18 | MySQL Server: Information schema | Not a Bug (6254 days) | S3 | 5.0.32 | Linux (Linux) | Any | GROUP BY groups `TEST` and `test` in I_S |
29900 | 2007-07-19 14:39 | 2013-03-03 20:45 | MySQL Server: Information schema | Verified (5169 days) | S3 | 5.1.21-23 | Any | Any | MySQL does not return an error to the client if INFORMAT SCHEMA fill table fails |
25630 | 2007-01-15 15:59 | 2018-09-09 20:45 | MySQL Server: Information schema | Verified (5363 days) | S3 | 5.0.33-standard-log/5.1BK | Linux (Centos 4.x) | Any | INFORMATION_SCHEMA collation wrong for filesystems with case sensitive filenames |
26182 | 2007-02-08 11:02 | 2015-07-09 13:30 | MySQL Server: Information schema | Verified | S3 | 6.0 | Any | Any | patch: process percentage of a process -- contributed from Jeremy Cole |
32099 | 2007-11-05 10:16 | 2007-12-14 13:38 | MySQL Server: Information schema | Can't repeat (5950 days) | S1 | 5.1.22-RC | Linux | Any | Crash when selecting from INFORMATION_SCHEMA |
34529 | 2008-02-13 16:52 | 2008-07-18 15:48 | MySQL Server: Information schema | Closed (5733 days) | S2 | 6.0-BK | Any | Any | Crash on complex Falcon I_S select after ALTER .. PARTITION BY |
81452 | 2016-05-17 6:06 | 2018-09-25 22:04 | MySQL Server: Information schema | Verified (2873 days) | S6 | 5.5.49 | Any | Any | InnoDB: Failing assertion: index->id == btr_page_get_index_id(page) |
82938 | 2016-09-10 8:23 | 2016-09-14 14:16 | MySQL Server: InnoDB storage engine | Not a Bug (2753 days) | S3 | 5.7 | Any | Any | Document are not correct in the case of innodb_support_xa=true. |
83085 | 2016-09-21 18:15 | 2016-10-22 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2716 days) | S1 | MYSQL 5.5.49 | Debian (x86_64) | Any | Insert after Left join generates duplicated rows in result |
87476 | 2017-08-18 14:27 | 2017-08-23 10:32 | MySQL Server: InnoDB storage engine | Can't repeat (2410 days) | S2 | 5.7.12 | Debian (8.5) | Any | Semaphore wait crash due to long held lock during online index creation |
87477 | 2017-08-18 14:27 | 2018-12-03 20:50 | MySQL Server: InnoDB storage engine | Duplicate (1943 days) | S2 | 5.7.12 | Debian (8.5) | Any | Semaphore wait crash due to long held lock during online index creation |
88121 | 2017-10-17 12:38 | 2017-10-17 13:12 | MySQL Server: InnoDB storage engine | Can't repeat (2355 days) | S2 | 5.6.37 | Linux | Any | MySQL crashes in btr_pcur_restore_position_func at btr0pcur.cc |
99295 | 2020-04-18 7:56 | 2020-04-20 10:04 | MySQL Server: InnoDB storage engine | Verified (1439 days) | S2 | 8.0.19 | Any | Any | InnoDB in-memory estimate is wrong after an index is created |
99714 | 2020-05-28 3:30 | 2020-07-06 12:01 | MySQL Server: InnoDB storage engine | Not a Bug (1365 days) | S3 | 8.0.15 | Linux | Any | Updates to JSON column type are not |
52590 | 2010-04-05 5:10 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5068 days) | S1 | 5.5.4-m3 | Any | Any | Assertion heap_no == ULINT_UNDEFINED in lock/lock0lock.c line 3695 |
39730 | 2008-09-29 14:30 | 2008-10-04 14:14 | MySQL Server: InnoDB storage engine | Duplicate (5655 days) | S1 | 5.0.67 | Windows (XP 5.1.2600) | Any | Query Crash Mysql Server 5.0.67 |
56190 | 2010-08-23 14:23 | 2013-08-25 20:45 | MySQL Server: InnoDB storage engine | Verified | S4 | 5.1.50, 5.5.5 | Any | Any | improve error messages for 'the age of the last checkpoint ..which exceeds the ' |
61917 | 2011-07-19 19:41 | 2011-07-19 20:19 | MySQL Server: InnoDB storage engine | Not a Bug (4637 days) | S1 | 5.5.13-enterprise-commercial-advanced-lo | Windows | Any | Unable to save result of a sum into a local variable in a stored proc |
67196 | 2012-10-11 21:00 | 2012-10-12 12:22 | MySQL Server: InnoDB storage engine | Verified (4186 days) | S3 | 5.5, 5.6 | Any | Any | ENUM type not treated correctly in HAVING w/ MAX() |
69168 | 2013-05-07 19:20 | 2013-09-18 6:38 | MySQL Server: InnoDB storage engine | Closed (3845 days) | S2 | 5.6.11, 5.6.12 | Any (FreeBSD, Linux) | Any | COUNT(*)...GROUP BY sometimes returns wrong results on partitioned InnoDB tables |
73168 | 2014-07-02 4:14 | 2015-02-25 10:51 | MySQL Server: InnoDB storage engine | Verified (3558 days) | S5 | 5.6/5.7 | Any | Any | locking/unlocking overhead for THD::LOCK_thd_data |
73202 | 2014-07-05 0:31 | 2014-12-04 16:20 | MySQL Server: InnoDB storage engine | Closed (3413 days) | S3 | 5.6, 5.7.5 | Any | Any | write/sync redo log before flush thread cache to binlog |
80898 | 2016-03-30 5:00 | 2016-11-16 6:49 | MySQL Server: InnoDB storage engine | Closed (2919 days) | S3 | 5.7 | Any | Any | Replication stops after transaction is rolled back asynchronously in master |
39905 | 2008-10-07 10:43 | 2008-10-07 11:31 | MySQL Server: InnoDB storage engine | Not a Bug (5652 days) | S3 | 5.0 | Any | Any | Incorrect result with HAVING and no GROUP BY |
107700 | 2022-06-29 11:18 | 2022-08-08 22:48 | MySQL Server: InnoDB storage engine | Verified (612 days) | S5 | 8.0.29 | Any | Any | Performance of Temptable is worse than Memory in GROUP BY scenario |
2249 | 2004-01-01 13:33 | 2004-01-02 6:39 | MySQL Server: InnoDB storage engine | Can't repeat (7392 days) | S1 | 4.1.0-alpha | Linux (Linux Redhat 8.0) | Any | Signal 11 Running Join Query |
98782 | 2020-02-28 18:57 | 2020-07-20 8:31 | MySQL Server: InnoDB storage engine | Can't repeat (1348 days) | S5 | 8.0.19 | Any | Any | Using TempTable engine for GROUP BY is slower than using MEMORY engine |
114248 | 2024-03-06 16:22 | 2024-03-07 14:05 | MySQL Server: InnoDB storage engine | Verified (22 days) | S3 | 8.0.36, 5.7.44 | Any | Any | Incomplete query results when backward scan and concurrent page merge |
68079 | 2013-01-14 12:01 | 2014-02-28 6:40 | MySQL Server: InnoDB storage engine | Closed (3725 days) | S2 | 5.5.29, 5.6.9-rc | Linux (x86_64) | Any | InnoDB does not scale well on 12 core system for specific all in memory SELECT |
55626 | 2010-07-29 13:20 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4854 days) | S3 | all | Any | Any | MIN and MAX reading a delete-marked record from secondary index |
57804 | 2010-10-28 12:21 | 2013-12-20 12:58 | MySQL Server: InnoDB storage engine | Closed (3752 days) | S3 | 5.6 | Any | Any | enabling monitor counter from my.cnf |
58015 | 2010-11-05 13:22 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4825 days) | S2 | 5.6.1 | Any | Any | Assert in row_sel_field_store_in_mysql_format when running innodb_mrr_icp test |
58219 | 2010-11-16 7:23 | 2013-10-28 12:51 | MySQL Server: InnoDB storage engine | Can't repeat (3805 days) | S3 | 5.5 | Any | Any | segfault in row_search_for_mysql for INSERT SELECT |
58404 | 2010-11-22 21:46 | 2012-10-15 13:30 | MySQL Server: InnoDB storage engine | Closed (4183 days) | S2 | 5.6.1-m5-debug | Any | Any | Assertion prev_view == NULL || prev_view->low_limit_no >= view->low_limit_no |
58815 | 2010-12-08 13:12 | 2016-12-01 8:21 | MySQL Server: InnoDB storage engine | Can't repeat (4458 days) | S2 | 5.5, 5.6.3 | Any | Any | btr_estimate_n_rows_in_range_on_level() can read a freed page |
59488 | 2011-01-13 23:12 | 2011-08-03 15:06 | MySQL Server: InnoDB storage engine | Closed (4622 days) | S2 | 5.6.1-m5 | Any | Any | Error trying to access page and assertion in fil0fil.c line 4407 with ICP on |
59505 | 2011-01-14 14:14 | 2013-02-19 13:42 | MySQL Server: InnoDB storage engine | Can't repeat (4056 days) | S3 | 5.6 | Any | Any | abort in que_thr_stop_for_mysql_no_error |
59845 | 2011-01-31 14:03 | 2014-07-17 8:25 | MySQL Server: InnoDB storage engine | Can't repeat (3543 days) | S3 | 5.5+ | Any | Any | Abort in lock_rec_insert_check_and_lock for CREATE TABLE ... SELECT |
60042 | 2011-02-09 9:50 | 2012-01-05 0:19 | MySQL Server: InnoDB storage engine | Closed (4467 days) | S1 | 5.6.2-m5 (mysql-next-mr-opt-backporting) | Any | Any | Crash in ha_innobase::open |
61188 | 2011-05-16 16:43 | 2011-11-02 16:32 | MySQL Server: InnoDB storage engine | Closed (4531 days) | S3 | 5.5.12-log | Linux (CentOS release 5.3 (Final)) | Any | DROP TABLE extremely slow |
61710 | 2011-06-30 16:38 | 2011-07-30 23:00 | MySQL Server: InnoDB storage engine | No Feedback (4626 days) | S1 | 5.5.9 | Linux | Any | MySQL segmentation fault |
65429 | 2012-05-26 14:51 | 2015-04-23 11:32 | MySQL Server: InnoDB storage engine | Won't fix (3263 days) | S3 | 5.5, 5.6 | Any | Any | Assertion failure block->page.space == page_get_space_id(page_align(ptr)) |
68133 | 2013-01-21 14:54 | 2013-04-20 13:19 | MySQL Server: InnoDB storage engine | Closed (3996 days) | S4 | 5.6.9 | Any | Any | Leftover prototype for the removed srv_parse_log_group_home_dirs() |
69141 | 2013-05-03 22:56 | 2013-09-20 4:38 | MySQL Server: InnoDB storage engine | Closed (3844 days) | S3 | 5.6-debug, 5.7-debug | Linux (Ubuntu 12.04 64-bit) | Any | SELECT from InnoDB table hangs being run in parallel with replicating LOAD DATA |
69477 | 2013-06-14 19:06 | 2014-09-19 17:06 | MySQL Server: InnoDB storage engine | Closed (3595 days) | S2 | All | Any | Any | InnoDB: Use of large externally-stored fields makes crash recovery lose data |
69979 | 2013-08-10 9:59 | 2021-04-02 12:37 | MySQL Server: InnoDB storage engine | Not a Bug (3769 days) | S1 | 5.0 | Any | Any | columns with unique key gets intermittent duplicate values! |
73322 | 2014-07-18 8:31 | 2016-09-27 13:15 | MySQL Server: InnoDB storage engine | Closed (2740 days) | S1 | 5.6.19 | Linux (CentOS 6.5) | Any | SEGFAULT while selecting from table with limit 1000 |
76927 | 2015-05-04 12:09 | 2016-06-18 21:26 | MySQL Server: InnoDB storage engine | Closed (3147 days) | S2 | 5.1, 5.5, 5.6, 5.7, 8.0 | Any | Any | Duplicate UK values in READ-COMMITTED (again) |
77102 | 2015-05-20 11:53 | 2015-05-21 13:06 | MySQL Server: InnoDB storage engine | Not a Bug (3235 days) | S2 | 5.7 | Any | Any | 5.7 Introduces CREATE TABLESPACE with different syntax than 5.1-5.6 |
77588 | 2015-07-01 19:56 | 2018-02-06 15:14 | MySQL Server: InnoDB storage engine | No Feedback (3122 days) | S2 | 5.6.25 | Any | Any | InnoDB: Failing assertion: index->table->stat_initialized |
80654 | 2016-03-08 7:31 | 2018-10-24 12:23 | MySQL Server: InnoDB storage engine | Unsupported (1983 days) | S2 | 5.7.11 | Linux (ppc64le ubuntu 14.04) | ARM | assertion srv_get_task_queue_length() == 0 trx0purge.cc line 1770 |
4159 | 2004-06-16 4:17 | 2004-09-09 16:44 | MySQL Server: InnoDB storage engine | Can't repeat (7141 days) | S1 | 4.0.20-max binary | Linux (Linux version 2.4.20-31.9smp) | Any | Ciritical Innodb shutdown ( about ha_innodb.cc ) |
7051 | 2004-12-06 20:03 | 2004-12-07 14:05 | MySQL Server: InnoDB storage engine | Closed (7052 days) | S1 | 4.1.7 gamma max | Windows (windows XP) | Any | mysql-max.exe Crash |
10447 | 2005-05-08 13:32 | 2005-05-25 19:55 | MySQL Server: InnoDB storage engine | Can't repeat (6883 days) | S1 | 4.0.21 | Linux (Redhat Enterprise ES 3 (Taroon)) | Any | Corrupted table space after 600 sec semaphore wait |
16843 | 2006-01-27 14:32 | 2006-01-28 10:08 | MySQL Server: InnoDB storage engine | Closed (6635 days) | S2 | 4.0.18 | Linux (SLES8) | Any | MySQL-Server dies if InnoDB-Buffer-Pool-Size grows up |
103317 | 2021-04-14 11:50 | 2021-04-15 5:22 | MySQL Server: InnoDB storage engine | Duplicate (1079 days) | S6 | 8.0.18/8.0.22/8.0.23 | Any | Any | Using temptable, query with many columns and group by clause alerts 1022 error |
307 | 2003-04-18 11:28 | 2019-05-14 14:21 | MySQL Server: InnoDB storage engine | Closed (7648 days) | S2 | 4.1 | Linux (Redhat Linux 8) | Any | InnoDB UNION with WHERE on indexed TIMESTAMP crashes everytime |
455 | 2003-05-20 3:06 | 2003-05-21 10:02 | MySQL Server: InnoDB storage engine | Closed (7618 days) | S3 | Alpha 4.1 | Linux (Linux RedHat 7.1 (ODBC Win2k)) | Any | MAX on Order By |
1262 | 2003-09-12 8:10 | 2003-10-21 9:50 | MySQL Server: InnoDB storage engine | Not a Bug (7465 days) | S2 | 4.0.11a | Linux (Mandrake Linux 9.1) | Any | LEFT JOIN of a table with an INNER JOIN returns cartesian product |
1451 | 2003-09-30 16:24 | 2003-10-03 1:20 | MySQL Server: InnoDB storage engine | Closed (7483 days) | S2 | 4.0.13 | Any | Export Table Creation - Error with Foreign Key | |
1708 | 2003-10-30 0:56 | 2003-11-02 7:33 | MySQL Server: InnoDB storage engine | Closed (7453 days) | S2 | 4.1.1 (2003-10-30) | Any | InnoDB crash on a subquery | |
1800 | 2003-11-11 0:23 | 2003-11-13 15:07 | MySQL Server: InnoDB storage engine | Duplicate (7442 days) | S2 | 4.1 alpha | Windows (xp and 2k) | Any | Problem with subquery |
20866 | 2006-07-05 13:49 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5033 days) | S1 | 5.1.12 | Linux (Ubuntu 5.10) | Any | show table status on innodb raises assertion |
32083 | 2007-11-03 22:53 | 2008-02-25 19:15 | MySQL Server: InnoDB storage engine | Closed (5877 days) | S1 | 5.0.50 | Any | Any | server crashes on show status when InnoDB is not initialized |
39168 | 2008-09-01 19:54 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (4915 days) | S2 | any | Any | Any | ERROR: the age of the last checkpoint ... exceeds the log group capacity |
40195 | 2008-10-21 8:35 | 2008-10-21 17:46 | MySQL Server: InnoDB storage engine | Not a Bug (5638 days) | S5 | 5.1.28 | Linux (SLES10) | Any | Slowdown queries by the use of groupby in Innodb |
46004 | 2009-07-07 12:33 | 2012-05-18 20:19 | MySQL Server: InnoDB storage engine | Duplicate (4932 days) | S2 | 5.1 | Any | Any | Crash in row_sel_field_store_in_mysql_format on a SELECT + LIMIT |
85119 | 2017-02-22 3:08 | 2022-03-15 15:38 | MySQL Server: InnoDB storage engine | Unsupported (745 days) | S4 | 5.6 5.7 | Any | Any | Innodb needs an instant checksum. |
95932 | 2019-06-23 14:37 | 2019-06-25 8:51 | MySQL Server: InnoDB storage engine | Can't repeat (1739 days) | S2 | 5.5 | Linux (own os based on linux 64bit) | x86 | mysqld got signal 11 |
96071 | 2019-07-02 10:43 | 2022-07-19 13:12 | MySQL Server: InnoDB storage engine | Verified (1388 days) | S3 | 8.0.16 | Any | Any | TempTable engine uses much more memory than MEMORY engine for temporary table |
99100 | 2020-03-27 13:22 | 2021-11-12 14:28 | MySQL Server: InnoDB storage engine | Closed (954 days) | S2 | 8.0 | Any | Any | GROUP BY will throw table is full when temptable memory allocation exceed limit |
154 | 2003-03-15 5:44 | 2003-03-15 23:28 | MySQL Server: InnoDB storage engine | Closed (7685 days) | S2 | All | Any | Wrong group by or distinct on Innodb table indexed column with NULLs | |
1703 | 2003-10-29 10:12 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7090 days) | S3 | 4.0.12 | Linux (Slackware linux) | Any | SELECT DISTINCT not showing a distinct row |
13669 | 2005-09-30 19:18 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5343 days) | S4 | 5.0 | Any (all) | Any | Group commit is broken in 5.0 |
26995 | 2007-03-09 12:20 | 2007-05-10 16:05 | MySQL Server: InnoDB storage engine | No Feedback (6168 days) | S2 | 5.0.16-nt | Windows (Win XP) | Any | Recordset Does Not Select the Value from View in MySQL 5.0.16-nt |
32455 | 2007-11-16 18:29 | 2007-11-16 22:40 | MySQL Server: InnoDB storage engine | Can't repeat (5978 days) | S3 | 5.0.45-log | FreeBSD | Any | Problem in innodb with a HAVING xxx IS NULL While using a GROUP BY |
46650 | 2009-08-11 12:51 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5031 days) | S1 | 5.1,5.4 | Any | Any | Innodb assertion autoinc_lock == lock in lock_table_remove_low on INSERT SELECT |
52431 | 2010-03-29 11:03 | 2018-09-23 20:45 | MySQL Server: InnoDB Plugin storage engine | Duplicate (5105 days) | S2 | mysql-trunk-runtime-exp | Any | Any | Crash in innobase_build_index_translation on SHOW TABLE STATUS |
54220 | 2010-06-03 22:22 | 2018-09-23 20:45 | MySQL Server: InnoDB Plugin storage engine | Duplicate (4986 days) | S2 | mysql-trunk, mysql-next-mr, 5.5.4-m3 | Any | Any | Corruption or crash on SELECT FROM I_S + ALTER TABLE with innodb_file_per_table |
54678 | 2010-06-21 19:43 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (4861 days) | S2 | 5.1,5.5.5-m3 | Any | Any | InnoDB, TRUNCATE, ALTER, I_S SELECT, crash or deadlock |
62030 | 2011-07-29 18:17 | 2014-05-14 12:37 | MySQL Server: InnoDB Plugin storage engine | Closed (3607 days) | S5 | 5.6.3 | Any | Any | trx_sys_flush_max_trx_id stalls transaction start |
62210 | 2011-08-19 11:47 | 2012-02-02 19:59 | MySQL Server: InnoDB Plugin storage engine | Can't repeat (4439 days) | S2 | 5.1.48 (1.0.9) | Linux (2.6.18-164.el5) | Any | memory corruption for THD after deadlock in foreign key reference constrain |
63270 | 2011-11-15 20:39 | 2018-10-01 16:17 | MySQL Server: InnoDB Plugin storage engine | Closed (4441 days) | S6 | Any | Any | Dirty read during crash recovery | |
110110 | 2023-02-17 12:25 | 2023-02-21 13:07 | MySQL Server: InnoDB Plugin storage engine | Can't repeat (402 days) | S3 | 8.0.31 | Red Hat (8.7) | x86 (Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz) | MGR SECONDARY UNREACHABLE |
968 | 2003-07-31 12:19 | 2003-08-01 1:11 | MySQL Server: Installing | Closed (7546 days) | S3 | Any | script needs fixing | ||
1421 | 2003-09-28 15:57 | 2003-09-28 18:09 | MySQL Server: Installing | Not a Bug (7488 days) | S1 | Windows (Windows 2000 Pro SVP4) | Any | Install crashes | |
3718 | 2004-05-11 19:02 | 2004-05-11 19:17 | MySQL Server: Installing | Not a Bug (7262 days) | S1 | 5.0 Alpha Preview | Windows (Windows 2003 Server 64 bit Exten) | Any | Cannot Install on Windows 2003 Server 64-bit Extended |
4109 | 2004-06-11 16:53 | 2004-08-26 6:06 | MySQL Server: Installing | Not a Bug (7155 days) | S2 | 4.0.20a | Windows (Windows 2000) | Any | Unable to Install V4.0.20a on Windows |
52591 | 2010-04-05 8:02 | 2014-03-14 18:38 | MySQL Server: Installing | Can't repeat (3668 days) | S3 | 5.5.3-m3 | Solaris (sparc) | Any | Server goes away (on Solaris) while mysql_upgrade when BLOB/TEXT data is used |
53915 | 2010-05-22 17:20 | 2016-12-13 13:51 | MySQL Server: Installing | Unsupported (2663 days) | S2 | 5.1.47 | Windows | Any | Installer does not not installer Documentation |
4215 | 2004-06-18 23:30 | 2012-05-18 20:19 | MySQL Server: Installing | Duplicate (7161 days) | S2 | 4.1.2 | REL 3 | Any | Intel 4.1.2 mysql_install_db fails |
7432 | 2004-12-20 15:00 | 2005-01-27 17:36 | MySQL Server: Installing | No Feedback (7001 days) | S2 | 4.0.22,4.1 | Windows (Windows) | Any | Error 132 at setup |
10681 | 2005-05-17 9:14 | 2005-05-25 2:42 | MySQL Server: Installing | Closed (6883 days) | S1 | 4.1.12 | Linux (SuSE 8.1 (2.4.21, i686)) | Any | Installation error (possibly help creation?) |
11389 | 2005-06-16 15:40 | 2005-06-18 3:59 | MySQL Server: Installing | Can't repeat (6859 days) | S3 | 4.0.21 and 4.0.24 | Windows (WINDOWS XP home edition with sp2) | Any | installationshield error _ins5176_mp appver 5.10.130.0 code 0xc0000005 adress 0 |
11443 | 2005-06-20 4:15 | 2005-09-16 23:47 | MySQL Server: Installing | Not a Bug (6769 days) | S1 | standard-4.1.12-pc-linux-gnu-i686 | Linux (Linux) | Any | ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/ |
12477 | 2005-08-10 1:01 | 2016-12-07 15:55 | MySQL Server: Installing | Unsupported (2669 days) | S4 | 5.0 | Linux (Linux) | Any | mysql_fix_privilege_tables does not use my.cnf exhaustively |
12821 | 2005-08-26 2:11 | 2005-09-26 10:29 | MySQL Server: Installing | No Feedback (6759 days) | S1 | 5.0.11 | Windows (Win 2000 Professional) | Any | Fail MySQL Server 5.11 install - Older version of MySQL 5.0 cannot be removed |
15865 | 2005-12-19 18:15 | 2013-08-29 1:00 | MySQL Server: Installing | No Feedback (3866 days) | S2 | 4.1.10a | Linux (Linux Fedora Core 4) | Any | /etc/init.d/mysql does not start mysqld at system start up |
80926 | 2016-03-31 15:17 | 2016-04-01 9:29 | MySQL Server: Installing | Verified (2919 days) | S3 | mysql.5.7.11, all | Linux | Any | mysqld_multi doesn't pass through defaults file related options |
67880 | 2012-12-12 1:20 | 2020-06-09 6:36 | MySQL Server: Installing | Verified (4125 days) | S1 | 5.6.9 | Windows | Any | mysql 5.6.9 on windows does not start if my.ini file is in utf8 format |
12348 | 2005-08-03 14:46 | 2005-08-08 16:20 | MySQL Server: Installing | Closed (6808 days) | S2 | 4.1.13 | Linux (CentOS 4.1) | Any | Installation RPM fails because of groupadd on CentOS Linux. |
18797 | 2006-04-05 12:55 | 2006-04-12 23:02 | MySQL Server: Installing | Closed (6561 days) | S3 | 5.0.17a-cert | Other (SCO OpenServer 6.0) | Any | Adding of default user/group for VOLS packages is not explicitly described |
19452 | 2006-04-30 23:49 | 2006-09-02 1:55 | MySQL Server: Installing | Closed (6418 days) | S3 | 5.0, 5.1 | Any | mysql_upgrade: reads [client] group, but doesn't understand host option | |
17157 | 2006-02-06 14:53 | 2006-03-08 2:22 | MySQL Server: Installing | Closed (6596 days) | S3 | 5.0.17a-cert | Solaris (Solaris10) | Any | pkg install on Solaris doesn't reject a user 'mysql' in group 'mysql2' |
10984 | 2005-05-31 14:11 | 2005-07-19 12:37 | MySQL Server: Installing | Closed (6828 days) | S3 | 4.0.20-0 | Linux (CentOS 3.4) | Any | install fails if group mysql exists but not user |
62205 | 2011-08-18 19:06 | 2012-01-15 19:11 | MySQL Server: Installing | Verified (4458 days) | S4 | 5.5.14 | Windows | Any | Installation of MySQL server for Windows ignores default socket parameters |
69482 | 2013-06-15 12:03 | 2013-06-17 13:29 | MySQL Server: Installing | Duplicate (3938 days) | S3 | 5.6.12 | MacOS (10.8.4) | Any | mysql_upgrade does not check it has sufficient file permissions |
110206 | 2023-02-24 11:54 | 2023-02-24 14:08 | MySQL Server: Installing | Can't repeat (399 days) | S3 | 8.0.32 | Windows (Server 2019) | Any | Upgrading MySQL Server from 8.0.27 to 8.0.32 using Installer 1.6.5.0 |
19737 | 2006-05-11 18:36 | 2006-05-12 17:09 | MySQL Server: Installing | Closed (6531 days) | S3 | 4.0-BK, 4.1-BK, 5.0-BK | Unix | Any | Some file modes too restrictive for other-user "make install" |
19738 | 2006-05-11 19:47 | 2006-10-04 2:41 | MySQL Server: Installing | Closed (6386 days) | S3 | 5.0, 5.1 | Any (Unix) | Any | "make install" tries to build files that "make" should already have built |
21949 | 2006-08-31 15:47 | 2007-06-12 8:28 | MySQL Server: Installing | No Feedback (6135 days) | S3 | 5.0.24 | Linux (RedHat Enterprise Linux AS4) | Any | RHEL4 installation bug |
23524 | 2006-10-21 7:11 | 2006-11-22 12:29 | MySQL Server: Installing | No Feedback (6337 days) | S2 | 5.0.24a-0.rhel3.i386.rpm | Linux (Linux 2.4.21-27.ELsmp) | Any | Starting MySQLCouldn't find MySQL manager or server [FAILED] |
30921 | 2007-09-09 23:04 | 2007-09-10 4:35 | MySQL Server: Installing | Closed (6045 days) | S3 | 1.2.12 | Windows (Vista) | Any | Config wizard creates 2 [mysqld] in my.ini |
5271 | 2004-08-27 22:23 | 2004-08-29 10:41 | MySQL Server: ISAM storage engine | Not a Bug (7152 days) | S3 | Ver 12.22 Distrib 4.0.20a, for Win95/Wi | Windows (win2k) | Any | Improperly optimized JOIN query |
93254 | 2018-11-20 3:33 | 2019-04-17 22:22 | MySQL Server: JSON | Closed (1808 days) | S3 | 5.7.24, 8.0.13 | Ubuntu | Other (x64) | MAX treating Numbers as Strings when used in group by and JSON_UNQUOTE |
84653 | 2017-01-24 21:03 | 2017-01-24 21:07 | MySQL Server: JSON | Duplicate (2621 days) | S4 | Any | Any | json aggregate functions | |
87854 | 2017-09-25 12:49 | 2017-09-30 5:24 | MySQL Server: JSON | Closed (2373 days) | S3 | 5.7, 8.0 | Any | Any | JSON_OBJECT creates invalid JSON code |
101048 | 2020-10-04 1:38 | 2024-02-27 13:51 | MySQL Server: JSON | Closed (100 days) | S3 | 8.0 | Any | Any | The result is inconsistent between join and group by |
79812 | 2015-12-30 18:22 | 2016-06-18 21:35 | MySQL Server: JSON | Not a Bug (2970 days) | S2 | 5.7.10, 8.0.0 | Any | Any | JSON_ARRAY and JSON_OBJECT return inproper JSON when used with GROUP_CONCAT |
63751 | 2011-12-14 20:06 | 2011-12-21 20:55 | MySQL Server: Locking | Not a Bug (4482 days) | S3 | 5.5.15 | Any | Any | "SELECT ... WHERE w_id%4=1 FOR UPDATE" locks whole table |
38804 | 2008-08-14 16:27 | 2008-10-17 18:16 | MySQL Server: Locking | Closed (5642 days) | S1 | 5.1-bzr | Any | Any | Query deadlock causes all tables to be inaccessible. |
46433 | 2009-07-28 15:10 | 2018-09-10 11:18 | MySQL Server: Locking | No Feedback (5319 days) | S2 | 6.0.12-bzr | Linux | Any | SHOW OPEN TABLES hangs waiting for lock |
46473 | 2009-07-30 10:57 | 2011-02-16 23:44 | MySQL Server: Locking | Can't repeat (5295 days) | S2 | 5.4 | Any | Any | Assertion in reference_table_share on concurrent SELECT on system tables |
49493 | 2009-12-07 9:20 | 2012-05-18 20:19 | MySQL Server: Locking | Duplicate (5226 days) | S3 | 6.0-codebase-bugfixing | Any | Any | assertion !table->file || table->file->inited == handler::NONE on DDL workload |
50406 | 2010-01-18 10:26 | 2017-05-07 20:45 | MySQL Server: Locking | Duplicate (5140 days) | S1 | next-mr, 6.0-codebase-bugfixing | Any | Any | Deadlock around system variables and the fill_status() function |
50589 | 2010-01-25 12:37 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5013 days) | S2 | next-mr, next-mr-4284 | Any | Any | Server hang on a query evaluated using a temporary table |
50912 | 2010-02-04 12:33 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5136 days) | S2 | mysql-next-4284 | Any | Any | Assertion `ticket->m_type >= mdl_request->type' failed on HANDLER + I_S |
51263 | 2010-02-18 1:10 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5000 days) | S2 | mysql-next-4284,5.5-m3 | Any | Any | Deadlock between transactional SELECT and ALTER TABLE ... REBUILD PARTITION |
52432 | 2010-03-29 11:25 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (4990 days) | S2 | trunk-runtime-exp, next-mr-wl5136-stage | Any | Any | Crash in check_table_is_closed on an information_schema query |
54811 | 2010-06-25 14:35 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (4978 days) | S3 | 5.5.5-m3 | Any | Any | assert in mysql_lock_have_duplicate |
13893 | 2005-10-10 10:59 | 2022-08-21 20:45 | MySQL Server: Locking | Duplicate (6519 days) | S1 | 5.0.13/5.0.16 BK source | Windows (WINXP/Linux) | Any | INSERTION BLOCKED (WITH TRIGGER) MEANWHILE A BIG SELECT ON THE TABLE IS RUNNING |
52356 | 2010-03-25 9:16 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5075 days) | S1 | Celosia (M3), Dahlia (M4) | Linux | Any | query_cache_debug fails on Linux |
54747 | 2010-06-23 16:06 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (4949 days) | S3 | 5.5.3-m3, 5.5.5-m3 | Any | Any | Deadlock between REORGANIZE PARTITION and SELECT is not detected |
98654 | 2020-02-19 6:42 | 2020-02-20 6:34 | MySQL Server: Logging | Verified (1499 days) | S4 | 8.0.19 | CentOS (7.4) | x86 | Reopen function for GSC_DEBUG_TRACE |
47421 | 2009-09-17 21:07 | 2011-02-16 23:44 | MySQL Server: Logging | Closed (5251 days) | S3 | 5.4/6.0 | Any | Any | Server crash from - SELECT SUM ( DISTINCT <char_column>) in azalea |
57406 | 2010-10-12 14:40 | 2012-11-14 14:12 | MySQL Server: Logging | Closed (4153 days) | S2 | 5.5.6 & 5.1.49, 5.1.51 | Linux | Any | UMASK is ignored by error log |
68929 | 2013-04-11 9:41 | 2014-03-28 19:37 | MySQL Server: Logging | Closed (3654 days) | S3 | 5.6.10 | Any | Any | Crash injection site crash_commit_before_unlog either misplaced, either misnamed |
109034 | 2022-11-09 4:15 | 2022-11-14 14:45 | MySQL Server: Logging | Verified (501 days) | S4 | 8.0 | Any | Any | Slow log Rows_examined value is inaccurate |
67089 | 2012-10-04 18:50 | 2014-11-19 7:51 | MySQL Server: Logging | Verified (3418 days) | S4 | 5.1.54, 5.6.21 | Any | Any | Mysql error log group owned by root. |
39210 | 2008-09-03 11:19 | 2009-01-09 14:58 | MySQL Server: Maria storage engine | Closed (5558 days) | S1 | 5.1-maria, 6.0-maria | Any | Any | Maria deadlock in _ma_bitmap_wait_or_flush |
39446 | 2008-09-15 8:49 | 2020-09-13 20:45 | MySQL Server: Maria storage engine | Duplicate (5631 days) | S1 | 6.0-bzr | Any | Any | Maria deadlock in pagecache_read |
39665 | 2008-09-26 12:02 | 2009-01-08 11:09 | MySQL Server: Maria storage engine | Closed (5559 days) | S3 | 5.1-maria | Linux | Any | Maria: assertion in block format during table scan |
39710 | 2008-09-28 11:34 | 2009-01-08 11:05 | MySQL Server: Maria storage engine | Closed (5559 days) | S1 | 5.1-maria, 6.0-maria | Any | Any | Maria assertion in maria_disable_non_unique_index |
40425 | 2008-10-30 11:50 | 2008-12-17 10:30 | MySQL Server: Maria storage engine | Can't repeat (5581 days) | S1 | 6.0 | Any | Any | Maria: ha_maria::enable_indexes(uint): Assertion `0' failed. |
40579 | 2008-11-07 15:20 | 2009-03-10 14:39 | MySQL Server: Maria storage engine | Closed (5498 days) | S3 | 5.1-maria | Any | Any | Maria: assertion in page cache in check_and_set_lsn() |
40890 | 2008-11-20 15:49 | 2009-01-08 10:38 | MySQL Server: Maria storage engine | Closed (5559 days) | S1 | 6.0.8-release | Any | Any | maria: Server crashes in sysbench OLTP_RW test at ctype-bin.c:8 |
40895 | 2008-11-20 16:39 | 2009-01-08 10:39 | MySQL Server: Maria storage engine | Closed (5559 days) | S1 | 6.0.8-release | Any | Any | maria: Server crashes in sysbench OLTP_RO test at lf_alloc-pin.c:367 |
41038 | 2008-11-25 22:49 | 2010-05-26 18:00 | MySQL Server: Maria storage engine | Unsupported (5056 days) | S3 | 6.0-maria | Any | Any | Maria: assertion in free_block() when dropping open table (pushbuild2) |
45865 | 2009-06-30 21:14 | 2010-05-26 18:01 | MySQL Server: Maria storage engine | Unsupported (5056 days) | S1 | 6.0.9-debug, 6.0.12-debug | Linux (32-bit fc8) | Any | assertion failure during maria tmp table destruction after group by and distinct |
68086 | 2013-01-15 8:41 | 2013-01-15 19:28 | MySQL Server: Memory storage engine | Verified (4091 days) | S3 | 5.5.29, 5.5.30, 5.7.1 | Any | Any | Heap tables don't use index for group by |
67978 | 2012-12-27 6:13 | 2012-12-29 16:21 | MySQL Server: Memory storage engine | Verified (4108 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Signed zero is handled incorrectly by HASH indexes and GROUP BY |
6853 | 2004-11-26 20:02 | 2008-10-08 9:46 | MySQL Server: Merge storage engine | Can't repeat (5651 days) | S2 | 5.0.0 | Linux (SLES9) | Any | MERGE Table Issue |
8092 | 2005-01-22 18:38 | 2013-07-03 5:38 | MySQL Server: Merge storage engine | Open | S4 | Any | Any | INSERT_METHOD feature request | |
4845 | 2004-08-01 11:44 | 2004-08-01 21:34 | MySQL Server: MyISAM storage engine | Closed (7180 days) | S1 | 4.1.3 beta | Windows (Windows 2003 server) | Any | Query failed (select count(id) cnt,title from udata where anketa=3 and qid=33 ) |
5269 | 2004-08-27 21:56 | 2004-10-30 1:01 | MySQL Server: MyISAM storage engine | Can't repeat (7090 days) | S2 | Any | Error 127 from query, check/repair report no problems | ||
5280 | 2004-08-28 13:09 | 2004-09-11 1:11 | MySQL Server: MyISAM storage engine | Can't repeat (7139 days) | S1 | 4.1.1. FreeBSD port: mysql-server-4.1.1_2 | FreeBSD (freebsd5.2.1) | Any | Complex query hangs server with signal 11 responce |
5411 | 2004-09-04 18:01 | 2004-11-26 7:25 | MySQL Server: MyISAM storage engine | Closed (7063 days) | S3 | 5.0.1-alpha snapshot | Windows (Windows XP) | Any | SQL Error 1030 / Error 124 during execution of sql statement |
5451 | 2004-09-07 15:22 | 2004-09-13 11:05 | MySQL Server: MyISAM storage engine | Not a Bug (7137 days) | S1 | 4.0.16-nt | Windows (Win 2k sp4) | Any | GROUP BY DESC not working |
« Show Previous 1000 Entries | Showing 1001-2000 of 2829 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |