Showing 1-30 of 89 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
105014 | 2021-09-23 3:32 | 2021-09-23 15:33 | MySQL Server: Partitions | Verified (1390 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 |
107556 | 2022-06-14 1:52 | 2022-06-14 8:20 | MySQL Server: Partitions | Verified (1126 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 (1197 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 (1231 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 (1280 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 (1314 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 (1344 days) | S3 | 8.0.27 | Any | Any | Empty loop brings loss to performance when pruning partitions for INSERT command |
105317 | 2021-10-26 6:12 | 2021-10-26 7:20 | MySQL Server: Partitions | Verified (1357 days) | S3 | 8.0.26, 8.0.27 | Any | Any | Behavior of auto-increment value after EXCHANGE PARTITION is inconsistent |
105204 | 2021-10-13 11:22 | 2021-11-01 8:41 | MySQL Server: Partitions | Verified (1370 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 (1370 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 (1372 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 (1384 days) | S3 | 5.7 | Any | Any | part field of unsigned bigint type |
107791 | 2022-07-07 7:01 | 2024-07-26 7:36 | MySQL Server: Partitions | Verified (1103 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 |
104981 | 2021-09-18 7:14 | 2021-09-20 6:44 | MySQL Server: Partitions | Verified (1393 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 (1397 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 (1404 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 (1410 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 (1579 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 (1657 days) | S3 | MySQL8.0.22/5.7 | Red Hat (rhel-7.4) | x86 (intel x86-64) | partitioned-table creation incorrectly checks timezone-dependent expressions |
101984 | 2020-12-13 14:28 | 2020-12-14 7:04 | MySQL Server: Partitions | Verified (1673 days) | S3 | 8.0.22, 5.7.32 | CentOS | x86 | partition by key distribute unbalance when PARTITIONS is even and some COLLATE |
101310 | 2020-10-26 4:39 | 2020-10-27 22:55 | MySQL Server: Partitions | Verified (1722 days) | S3 | 8.0.21, 8.0.22 | Any | Any | partition by key distribute unbalance for utf8 |
100810 | 2020-09-11 8:11 | 2020-09-14 18:46 | MySQL Server: Partitions | Verified (1764 days) | S1 | MySQL8.0.20 | Any (rhel-7.4) | Any (intel x86) | miss to check table definition for partitioned table while importing tablespace |
98231 | 2020-01-15 8:27 | 2020-03-11 13:52 | MySQL Server: Partitions | Verified (2005 days) | S3 | 8.0 | Any | Any | show index from a partition table gets a wrong cardinality value |
113700 | 2024-01-22 4:13 | 2024-01-22 8:45 | MySQL Server: Partitions | Verified (539 days) | S2 | 8.0.22, 8.0.36 | Any | Any | REORGANIZE PARTITION causes losing data |
118493 | 2025-06-20 6:54 | 2025-06-20 10:38 | MySQL Server: Partitions | Verified (24 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 (210 days) | S3 | 8.0.40 | Any | Any | Truncate partition not permit DML |
116791 | 2024-11-27 3:39 | 2024-11-27 9:04 | MySQL Server: Partitions | Verified (229 days) | S3 | 8.0.40 | Any | Any | Contribution by Tencent: add partition rollback crash |
116566 | 2024-11-06 6:23 | 2024-11-06 8:17 | MySQL Server: Partitions | Verified (250 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 (273 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 (350 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 |
Showing 1-30 of 89 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |