| Showing 1-50 of 90 (Edit, Save, CSV, Feed) | Show Next 50 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 104981 | 2021-09-18 7:14 | 2021-09-20 6:44 | MySQL Server: Partitions | Verified (1328 days) | S3 | 8.0.26 | Any | Any | Raise error that partition' name to be dropped doesn't exist at an earlier stage |
| 106884 | 2022-04-01 8:53 | 2022-05-24 20:59 | MySQL Server: Partitions | Verified (1132 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 (1166 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 (1215 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 (1249 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 (1279 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 (1292 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 (1305 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 (1305 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 (1307 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 (1319 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 (1325 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 (1061 days) | S2 | 8.0.29 | Any | Any | restore_object_from_record on partition table consumes too much memory |
| 104956 | 2021-09-16 8:54 | 2021-09-16 10:27 | MySQL Server: Partitions | Verified (1332 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 (1339 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 (1345 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 (1514 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 (1592 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 (1608 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 (1657 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 (1699 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 (1940 days) | S3 | 8.0 | Any | Any | show index from a partition table gets a wrong cardinality value |
| 97041 | 2019-09-26 16:20 | 2019-09-28 14:33 | MySQL Server: Partitions | Verified (2051 days) | S1 | 8.0+, 8.0.17, 5.7.27 | Any | Any | main&sub partition field order different from combined pk, query result lose row |
| 113419 | 2023-12-14 12:50 | 2023-12-18 10:47 | MySQL Server: Partitions | Verified (512 days) | S3 | 8.0 | Any | Any | Contribution by Tencent: partition prune ignore subpartition where condition |
| 116982 | 2024-12-16 3:16 | 2024-12-16 8:06 | MySQL Server: Partitions | Verified (145 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 (164 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 (185 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 (208 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 (285 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 (362 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 (417 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 (417 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 (470 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 (474 days) | S2 | 8.0.22, 8.0.36 | Any | Any | REORGANIZE PARTITION causes losing data |
| 96895 | 2019-09-17 5:45 | 2019-09-19 5:10 | MySQL Server: Partitions | Verified (2062 days) | S3 | 5.7.26 | Windows | Any | Test main.partition_rename_longfilename fails on Samba storage |
| 113369 | 2023-12-08 3:51 | 2024-01-05 13:06 | MySQL Server: Partitions | Verified (519 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 (520 days) | S3 | 8.0.34, 8.0.35 | Linux | Any | return error result with a qubquery |
| 112738 | 2023-10-16 9:26 | 2023-10-16 9:35 | MySQL Server: Partitions | Verified (572 days) | S1 | 8.0.30, 8.0.34 | Any | Any | can't truncate partition when partition_id exceed INT_MAX |
| 112181 | 2023-08-25 9:04 | 2023-09-18 8:39 | MySQL Server: Partitions | Verified (621 days) | S3 | 8.0 | Any | Any | TIMESTAMP(N) partitions doesn't prune for inequity |
| 111685 | 2023-07-07 1:13 | 2023-07-07 8:13 | MySQL Server: Partitions | Verified (673 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 (680 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 (789 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 (821 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 (823 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 (1038 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 |
| 67351 | 2012-10-24 8:02 | 2017-05-03 16:04 | MySQL Server: Partitions | Verified (4543 days) | S2 | 5.5.27-29.0 | Linux | Any | Cardinality samples of partitioned tables sometimes widely off |
| 72614 | 2014-05-12 0:42 | 2014-05-12 6:41 | MySQL Server: Partitions | Verified (4016 days) | S3 | 5.6.17, 5.6.19 | Any | Any | DATA DIRECTORY for partitioned tables |
| 72274 | 2014-04-08 11:45 | 2014-04-08 14:14 | MySQL Server: Partitions | Verified (4050 days) | S5 | 5.6.17 | Linux | Any | Allow DECIMAL as partitioning key and/or improve pruning for FLOOR(DECIMAL) |
| 72222 | 2014-04-03 14:21 | 2014-04-03 16:43 | MySQL Server: Partitions | Verified (4055 days) | S3 | mysql-5.5.35; mysql-5.6.16 | Linux | Any | Strange interaction of SQL_MODE=ANSI and partition by TIMESTAMP |
| 71947 | 2014-03-05 18:55 | 2014-03-06 5:18 | MySQL Server: Partitions | Verified (4083 days) | S3 | 5.6, 5.7 | Any | Any | Unexpected change in error code on INSERT .. PARTITION causes replication abort |
| Showing 1-50 of 90 (Edit, Save, CSV, Feed) | Show Next 50 Entries » |
