RE: rm RULE based optimizer != GOOD IDEA
- From: "Lex de Haan" <lex.de.haan@xxxxxxxxxxxxxx>
- To: <Ethan.Post@xxxxxx>, "'Pete Sharman'" <peter.sharman@xxxxxxxxxx>, "'Christian Antognini'" <Christian.Antognini@xxxxxxxxxxxx>
- Date: Fri, 22 Apr 2005 18:33:56 +0200
it is about maintaining the full code path behind the RBO, keeping it in all
regression tests, checking it over and over again on all platforms and all
releases -- and last but not least, produce bug fixes if they don't do the
testing properly.
and indeed, the SQL Tuning Advisor is able to call the CBO in Tuning mode, and
come back with a *statement specific* bunch of optimization goodies, aka SQL
profiles.
RBO is dead.
kind regards,
Lex.
---------------------------------------------
Visit my website at http://www.naturaljoin.nl
---------------------------------------------
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Post, Ethan
If there really is significant QA/Testing/Development that has to be done to
maintain the RBO then I understand but I would like to know the "truth" about
the matter. If the truth is that maintaining the RULE hint isn't all that more
complicated than maintaining the USE_HASH hint then I would like to see it stay.
Recall, my argument is that Oracle only maintain the hint at the SQL statement
level and that it does not need to be supported.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
