Re: Missing optimization when dealing with parittioned range partitions + MIN()/MAX() queries ?

This particular query is not equivalent for at least some reasons.
1) There is no quarantee, that data is available in the first partition at all (you can't consider fresh statistics as replacement for that) 2) You can get data in wrong partitions (for example by executing exchange partition without validation) 

Best regards

Maxim

On 08.02.2011 17:53, Nilo Segura wrote:

This particular query is equivalent to

explain plan for select min(z) from table2000 partition (tab_1999_h1);




--
http://www.freelists.org/webpage/oracle-l

Other related posts: