Re: Access and Filter Predicate on same execution plan line
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Wed, 18 Aug 2021 14:35:12 -0400
Message-ID: <37985284-a85f-4f0a-3861-f79b8d3898b0_at_gmail.com>
Date: Wed, 18 Aug 2021 14:35:12 -0400
Message-ID: <37985284-a85f-4f0a-3861-f79b8d3898b0_at_gmail.com>
On 8/18/21 8:02 AM, Jonathan Lewis wrote:
> Not true.
> But thanks to (relatively) recent changes in the costing of index skip
> scans it will appear this way if the number of index entries per value
> of the skipped column(s) is so small that that take less than two
> blocks (which often means you need 3 or 4 hundred rows per leading
> values)
Thanks Jonathan! If I understand you correctly, you are advocating putting the most selective column in order to avoid an expensive operation, not unlike FFS?
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com -- http://www.freelists.org/webpage/oracle-lReceived on Wed Aug 18 2021 - 20:35:12 CEST