[MDEV-41364] Partition HANDLER READ NEXT returns empty results when moving to the next partition - Jira

XML

Word

Printable

CREATE TABLE t1 (a INT, KEY(a)) ENGINE=InnoDB

PARTITION BY RANGE(a) (PARTITION p0 VALUES LESS THAN (10),

                       PARTITION p1 VALUES LESS THAN (20));

INSERT INTO t1 VALUES (5),(8),(15);

HANDLER t1 OPEN;

--echo # no row: KEY_NOT_FOUND, p0 cursor positioned at 8

HANDLER t1 READ a = (7);

--echo # expect 8, as without partitioning

HANDLER t1 READ a NEXT;

--echo # expect 15, as without partitioning, but output nothing

HANDLER t1 READ a NEXT;

HANDLER t1 CLOSE;

DROP TABLE t1;

blocks

MDEV-41764 Partitioning changes the query result: HANDLER READ NEXT after a read by key misses rows or returns them out of index order

relates to

MDEV-41764 Partitioning changes the query result: HANDLER READ NEXT after a read by key misses rows or returns them out of index order

split from

MDEV-41322 Regression: descending primary-key range scan on a partitioned InnoDB table fails with ERROR 1032

Estimated:

1.65d

Remaining:

1d 2.55h

Logged:

2.65h

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.