Bug #77782 valgrind error (conditional jump) when insert rows into a partitioned table
Submitted: 20 Jul 2015 6:32 Modified: 27 Jul 2015 13:05
Reporter: Benny Wang Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Optimizer Severity:S2 (Serious)
Version:5.7.8 OS:Any
Assigned to: CPU Architecture:Any

[20 Jul 2015 6:32] Benny Wang 
Description:
Reproducible with latest debug and valgrind builds of mysql-5.7

How to repeat:
DROP TABLE t1;

CREATE TABLE t1 (
    id INT NOT NULL,
    store_id INT NOT NULL,
    x INT GENERATED ALWAYS AS (id + store_id)
)
PARTITION BY RANGE (store_id) (
    PARTITION p0 VALUES LESS THAN (6),
    PARTITION p1 VALUES LESS THAN (11),
    PARTITION p2 VALUES LESS THAN (16),
    PARTITION p3 VALUES LESS THAN (21)
);

INSERT INTO t1 VALUES(1, 2, default);
INSERT INTO t1 VALUES(3, 4, default);

INSERT INTO t1 VALUES(3, 12, default);
INSERT INTO t1 VALUES(4, 18, default);
[27 Jul 2015 13:05] Paul DuBois 
Noted in 5.7.9, 5.8.0 changelogs.

Valgrind errors could occur during partition pruning for tables
containing generated columns.
[27 Aug 2015 4:19] Erlend Dahl 
Bug#78189 was marked as a duplicate