[MDEV-2286] LP:711801 - Sporadic wrong result with mrr_sort_keys Created: 2011-02-02  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Philip Stoev (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug711801.xml    

 Description   

The following RQG command line reports

perl runall.pl -queries=1M --duration=300 --threads=2 --seed=time --reporter=QueryTimeout,Deadlock,Backtrace,ErrorLog --validator=Transformer --filter=conf/optimizer/dsmrr-cpk.ff --no-mask --mysqld=sql_mode=ONLY_FULL_GROUP_BY --mysqld=optimizer_search_depth=6 --debug --notnull --engine=InnoDB --mysqld=-join_cache_level=7 --grammar=conf/optimizer/optimizer_no_subquery.yy --queries=100000000 --mask=35033 --basedir=/home/philips/bzr/maria-5.3-mwl128 --seed=1296569756 --threads=1 --duration=900

reports a single query that returns different results with different execution plans. Issue is not repeatable with an MTR test case. Issue goes away with mrr_sort_keys=off,index_condition_pushdown=off .

 Comments   
Comment by Sergei Petrunia [ 2011-03-05 ]

Re: Sporadic wrong result with mrr_sort_keys
Philip,

I suspect that this could be the same issue as BUG#707925, for which I've already pushed the fix. Could you please re-test with current 5.3?

Comment by Philip Stoev (Inactive) [ 2011-03-06 ]

Re: Sporadic wrong result with mrr_sort_keys
No longer repeatable.

Comment by Rasmus Johansson (Inactive) [ 2011-12-13 ]

Launchpad bug id: 711801

Generated at Thu Feb 08 06:40:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.