Showing 1–50 of 100
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 105317 | 2021-10-26 6:12 | 2021-10-26 7:20 | MySQL Server: Partitions | Verified (1833 days) | S3 | 8.0.26, 8.0.27 | Any | Any | Behavior of auto-increment value after EXCHANGE PARTITION is inconsistent |
| 111685 | 2023-07-07 1:13 | 2023-07-07 8:13 | MySQL Server: Partitions | Verified (1214 days) | S3 | 8.0.32, 8.0.33 | Linux | x86 | ADD PARTITION with DATA DIRECTORY forces relocation of other partitions |
| 111582 | 2023-06-27 12:03 | 2023-06-30 10:33 | MySQL Server: Partitions | Verified (1221 days) | S3 | 8.0.33 | Any | Any | Query is incorrect after importing partition table with a different definition |
| 110341 | 2023-03-10 17:18 | 2023-03-16 14:12 | MySQL Server: Partitions | Verified (1330 days) | S3 | 8.0.32 | Any | Any | FOUND_ROWS() gives wrong result on prepared query against partitioned table |
| 109994 | 2023-02-08 19:44 | 2023-02-09 5:35 | MySQL Server: Partitions | Verified (1362 days) | S3 | 5.7, 8.0 | Any | Any | Unexpected 1748 error returns when update stored generated column partition key |
| 109939 | 2023-02-05 9:23 | 2023-02-07 9:19 | MySQL Server: Partitions | Verified (1364 days) | S3 | 8.0.32, 5.7.41 | Any | Any | Lists partitions can not be reorganized (must be in consecutive order) |
| 107791 | 2022-07-07 7:01 | 2024-07-26 7:36 | MySQL Server: Partitions | Verified (1579 days) | S3 | 8.0.29, 8.0.39, 8.4.2, 9.0.1 | Any | Any | Left join with derived partitioned table returns wrong result |
| 107556 | 2022-06-14 1:52 | 2022-06-14 8:20 | MySQL Server: Partitions | Verified (1602 days) | S2 | 8.0.29 | Any | Any | restore_object_from_record on partition table consumes too much memory |
| 106884 | 2022-04-01 8:53 | 2022-05-24 20:59 | MySQL Server: Partitions | Verified (1673 days) | S2 | 8.0, 8.0.28 | Any | Any | Data are not repartitioned when the partition key's charset is modified |
| 106609 | 2022-03-01 8:11 | 2022-03-02 1:55 | MySQL Server: Partitions | Verified (1707 days) | S3 | 8.0.27, 5.7 | Any | Any | For EXCHANGE PARTITION, make partition table writable while validation |
| 106039 | 2022-01-05 7:08 | 2022-01-11 6:10 | MySQL Server: Partitions | Verified (1756 days) | S5 | 8.0.27 | Any | Any | Skip using priority queue and visiting unused partitions when single partition |
| 105801 | 2021-12-05 3:35 | 2021-12-08 14:16 | MySQL Server: Partitions | Verified (1790 days) | S5 | 5.7 | Any | Any | ha_innopart::records_in_range spend too much cpu cost |
| 105490 | 2021-11-08 11:28 | 2022-01-26 8:45 | MySQL Server: Partitions | Verified (1820 days) | S3 | 8.0.27 | Any | Any | Empty loop brings loss to performance when pruning partitions for INSERT command |
| 112181 | 2023-08-25 9:04 | 2023-09-18 8:39 | MySQL Server: Partitions | Verified (1162 days) | S3 | 8.0 | Any | Any | TIMESTAMP(N) partitions doesn't prune for inequity |
| 105204 | 2021-10-13 11:22 | 2021-11-01 8:41 | MySQL Server: Partitions | Verified (1846 days) | S3 | 8.0.26 | Any | Any | ha_innopart traverse all partitions instead of only used partitions causing loss |
| 105202 | 2021-10-13 10:02 | 2021-10-13 10:52 | MySQL Server: Partitions | Verified (1846 days) | S3 | 8.0.26, 5.7.35 | Any | Any | ha_innopart::store_lock() traverse all partitions starting from index 1 not 0 |
| 105186 | 2021-10-11 9:40 | 2021-10-11 10:41 | MySQL Server: Partitions | Verified (1848 days) | S2 | 8.0.26, 5.7.35 | Any | Any | a null value is not treated as zero in hash partition table |
| 105075 | 2021-09-29 13:00 | 2021-09-29 13:35 | MySQL Server: Partitions | Verified (1860 days) | S3 | 5.7 | Any | Any | part field of unsigned bigint type |
| 105014 | 2021-09-23 3:32 | 2021-09-23 15:33 | MySQL Server: Partitions | Verified (1866 days) | S1 | 8.0.25, 8.0.26, 8.0.11, 5.7.35 | Any (rhel-7.4) | Any (x86-64) | query gets incorrect resultset from table with subpartitions |
| 104981 | 2021-09-18 7:14 | 2021-09-20 6:44 | MySQL Server: Partitions | Verified (1869 days) | S3 | 8.0.26 | Any | Any | Raise error that partition' name to be dropped doesn't exist at an earlier stage |
| 104956 | 2021-09-16 8:54 | 2021-09-16 10:27 | MySQL Server: Partitions | Verified (1873 days) | S3 | 8.0.26, 5.7.35 | Any | Any | SHOW CREATE TABLE outputs are inconsistent after CREATE TABLE and ALTER TABLE |
| 104881 | 2021-09-09 8:25 | 2021-09-15 8:46 | MySQL Server: Partitions | Verified (1880 days) | S3 | 8.0.26, 5.7.35 | Any | Any | partition_info::set_used_partition not raise error when finding no partition |
| 104819 | 2021-09-03 6:55 | 2021-09-03 12:17 | MySQL Server: Partitions | Verified (1886 days) | S3 | 8.0 | Any | Any | partition table maxvalue define error |
| 103029 | 2021-03-18 6:34 | 2021-03-19 13:02 | MySQL Server: Partitions | Verified (2055 days) | S3 | 8.0 | Any | Any | Suboptimal plan due to null partition catch |
| 102090 | 2020-12-30 7:13 | 2020-12-30 9:35 | MySQL Server: Partitions | Verified (2133 days) | S3 | MySQL8.0.22/5.7 | Red Hat (rhel-7.4) | x86 (intel x86-64) | partitioned-table creation incorrectly checks timezone-dependent expressions |
| 116791 | 2024-11-27 3:39 | 2024-11-27 9:04 | MySQL Server: Partitions | Verified (705 days) | S3 | 8.0.40 | Any | Any | Contribution by Tencent: add partition rollback crash |
| 121400 | 2026-09-30 2:01 | 2026-09-30 2:14 | MySQL Server: Partitions | Open (33 days) | S2 | 8.0.24, 9.4 | Any | Any | Wrong result after extended secondary-index lookup on a partitioned InnoDB table |
| 121284 | 2026-09-15 6:13 | 2026-09-15 6:48 | MySQL Server: Partitions | Open | S2 | MySQL 9.7.2 and 26.7.0 | Any (Linux on x86_64) | Any | EXCHANGE PARTITION accepts mismatched functional indexes and causes wrong results |
| 121162 | 2026-08-23 7:59 | 2026-08-23 7:59 | MySQL Server: Partitions | Open | S1 | 9.7.1 | Any | Any | EXCHANGE PARTITION definition check ignores expressions and CHECK constraints |
| 121116 | 2026-08-18 11:25 | 2026-08-18 11:25 | MySQL Server: Partitions | Open | S2 | 9.7.1 | MacOS | ARM | index scan on a subpartitioned table silently omits rows when a secondary index contains a VIRTUAL generated column |
| 119965 | 2026-03-02 11:56 | 2026-03-02 13:58 | MySQL Server: Partitions | Verified (245 days) | S3 | 8.0.35 | Any | Any | The results of the same query statement are inconsistent when it is executed multiple times. |
| 119945 | 2026-02-26 2:44 | 2026-02-26 2:44 | MySQL Server: Partitions | Open | S3 | 8.0.35 | Any | Any | Inconsistent result set on repeated execution of NATURAL JOIN with expression index and KEY partitioning |
| 119938 | 2026-02-25 7:36 | 2026-03-04 3:50 | MySQL Server: Partitions | Verified (243 days) | S2 | 8.0.45, 8.4.8, 9.6.0 | Any | Any | select partition table with virtual column return wong result |
| 119859 | 2026-02-09 7:25 | 2026-02-09 8:06 | MySQL Server: Partitions | Verified (266 days) | S3 | 8.0.35 | Any | Any | Inconsistent Query Results Between Partitioned and Non-Partitioned Tables |
| 119784 | 2026-01-27 0:53 | 2026-06-01 23:27 | MySQL Server: Partitions | Open (279 days) | S3 | 8.0.42 and later | Any | Any | Fix partition pruning with non-constant defaults regression |
| 119309 | 2025-11-05 13:37 | 2026-06-03 12:37 | MySQL Server: Partitions | Verified (286 days) | S3 | 8.0.42 | Any | Any | An insert prepared statement fails to write across partitions |
| 118493 | 2025-06-20 6:54 | 2025-06-20 10:38 | MySQL Server: Partitions | Verified (500 days) | S3 | 8.0, 8.0.42 | Any | Any | Subpartitions can not be pruned by conditions derived from equal propagation |
| 116982 | 2024-12-16 3:16 | 2024-12-16 8:06 | MySQL Server: Partitions | Verified (686 days) | S3 | 8.0.40 | Any | Any | Truncate partition not permit DML |
| 101984 | 2020-12-13 14:28 | 2020-12-14 7:04 | MySQL Server: Partitions | Verified (2149 days) | S3 | 8.0.22, 5.7.32 | CentOS | x86 | partition by key distribute unbalance when PARTITIONS is even and some COLLATE |
| 116566 | 2024-11-06 6:23 | 2024-11-06 8:17 | MySQL Server: Partitions | Verified (726 days) | S3 | 8.0.32, 8.0.40, 8.4.3, 9.1.0 | Any | Any | List partition prune get a wrong result |
| 116340 | 2024-10-11 0:39 | 2024-10-14 8:10 | MySQL Server: Partitions | Verified (749 days) | S3 | 8.0, 9.0, 8.0.39 | Any | Any | Importing a partition tablespace skip the data validation |
| 115711 | 2024-07-29 6:56 | 2024-09-03 11:09 | MySQL Server: Partitions | Verified (826 days) | S2 | 8.0, 8.0.30,8.0.39, 8.4.2, 9.0.1 | Any | Any | Contribution by Tencent: Virtual column cause empty result in subpartition |
| 114982 | 2024-05-13 11:47 | 2024-05-13 12:40 | MySQL Server: Partitions | Verified (903 days) | S2 | 8.0 | Any | Any | Query result about list partition table is incorrect |
| 114400 | 2024-03-19 9:34 | 2024-03-19 12:16 | MySQL Server: Partitions | Verified (958 days) | S3 | 8.0.32, 8.0.36 | Any | Any | Create partition table with DATA DIRECTORY execution result is incorrect |
| 114396 | 2024-03-19 2:54 | 2024-03-19 5:53 | MySQL Server: Partitions | Verified (958 days) | S2 | 8.0.22, 8.0.35, 8.0.36 | Any | Any | NULL is not treated as 0 for tables partitioned by key |
| 113750 | 2024-01-25 6:50 | 2024-01-26 10:12 | MySQL Server: Partitions | Verified (1011 days) | S2 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | stats of partitions could be empty after some kind of alter table DDL statements |
| 113700 | 2024-01-22 4:13 | 2024-01-22 8:45 | MySQL Server: Partitions | Verified (1015 days) | S2 | 8.0.22, 8.0.36 | Any | Any | REORGANIZE PARTITION causes losing data |
| 113419 | 2023-12-14 12:50 | 2023-12-18 10:47 | MySQL Server: Partitions | Verified (1053 days) | S3 | 8.0 | Any | Any | Contribution by Tencent: partition prune ignore subpartition where condition |
| 113369 | 2023-12-08 3:51 | 2024-01-05 13:06 | MySQL Server: Partitions | Verified (1060 days) | S3 | 8.0.34, 8.0.35 | Any | Any | In the hash partition table, the query result is error. |
| 113338 | 2023-12-05 11:16 | 2023-12-07 8:11 | MySQL Server: Partitions | Verified (1061 days) | S3 | 8.0.34, 8.0.35 | Linux | Any | return error result with a qubquery |
Showing 1–50 of 100
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.023 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.