Bug #31256 Test "partition_pruning" reports higher read count than expected
Submitted: 27 Sep 2007 18:55 Modified: 22 Oct 2007 8:58
Reporter: Joerg Bruehe Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1.22-rc OS:IBM AIX (+i5os, 32 bit)
Assigned to: Assigned Account CPU Architecture:Any

[27 Sep 2007 18:55] Joerg Bruehe
Description:
Found in the release build of 5.1.22-rc.

Difference seems to indicate that "partition pruning" (WL#2986) is not happening correctly in this package.

Issue is specific to the IBM compiler, 32 bit, used on AIX and i5os.

-------------------------------------------------------
*** /PATH/mysql-test/r/partition_pruning.result
--- /PATH/mysql-test/r/partition_pruning.reject
***************
*** 631,637
  delete from t2 where b > 5;
  show status like 'Handler_read_rnd_next';
  Variable_name Value
! Handler_read_rnd_next 1115
  show status like 'Handler_read_key';
  Variable_name Value
  Handler_read_key      0
--- 631,637
  delete from t2 where b > 5;
  show status like 'Handler_read_rnd_next';
  Variable_name Value
! Handler_read_rnd_next 1215
  show status like 'Handler_read_key';
  Variable_name Value
  Handler_read_key      0
***************
*** 645,651
  delete from t2 where b < 5 or b > 3;
  show status like 'Handler_read_rnd_next';
  Variable_name Value
! Handler_read_rnd_next 1115
  show status like 'Handler_read_key';
  Variable_name Value
  Handler_read_key      0
--- 645,651
  delete from t2 where b < 5 or b > 3;
  show status like 'Handler_read_rnd_next';
  Variable_name Value
! Handler_read_rnd_next 1215
  show status like 'Handler_read_key';
  Variable_name Value
  Handler_read_key      0
-------------------------------------------------------

How to repeat:
Found by running the test suite.
[22 Oct 2007 8:58] Alexey Kopytov
Not reproducible when the post-5.1.22-rc fixes for bug #28430 are applied.