db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mike matrigali <mikema...@gmail.com>
Subject is there an optimizer override to force multi-probe query plan?
Date Thu, 25 Jul 2013 15:41:54 GMT
Is there an optimizer override in 10.8 to force a multi-probe query plan?

If not, is there an override in the new work being done in trunk to 
force it?

Also if not, is there any suggestion of what the right syntax would be
to add it to the old style optimizer override?

It seems recently there have been a number of issues where user
expected multi-probe plan but for various reasons the system has
chosen another plan.  Some of these have been bugs, some of these
have been statistics out of date, and most recently the application
would prefer multi-probe for more concurrency even if the execution
is less efficient than full scan.


View raw message