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

From: Nilo Segura <nilosegura_at_gmail.com>
Date: Tue, 8 Feb 2011 18:35:12 +0100
Message-ID: <AANLkTinTkdoJ7u+qiCufk2CFAi1XjUF9F-ka+BMigCOH_at_mail.gmail.com>



Ok, after some kind replies, I understood why it has to run the partition range all. I did the mistake of generalizing a particular case I was handling.

thanks!

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Feb 08 2011 - 11:35:12 CST

Original text of this message