db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-937) Instability in wisconsin test
Date Fri, 30 Jun 2006 15:31:52 GMT

Oystein Grovlen - Sun Norway wrote:

> While it is good that we get this noise out of derbyall, it seems like 
> this fix covers up a problem that we do not quite understand.  As far as 
>  I have understood, it seems like the optimizer due to some timing 
> issues does not use the indexes.  I think we should file a JIRA for this 
> problem.

I was working under the assumption that the wisc diffs were the kinds of
issues we had seen in the past.  Where the optimizer had 2 different 
plans which were very close in costing, and due to slight differences in
estimates one plan was chosen over another.

If anyone has done the careful analysis of the different plans and found 
that there is a serious problem with the plans the optimizer was picking 
please go ahead and report a new bug with that info and how to reproduce.

My main concern was that spurious "expected" diffs means that almost 
everyone is just going to ignore any real future bug the test might
show up.

View raw message