Re: Access and Filter Predicate on same execution plan line
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Tue, 17 Aug 2021 19:44:50 -0400
Message-ID: <0ad88559-055a-c206-adf5-095f6484591b_at_gmail.com>
Date: Tue, 17 Aug 2021 19:44:50 -0400
Message-ID: <0ad88559-055a-c206-adf5-095f6484591b_at_gmail.com>
Unfortunately, there is also an unwritten rule about the most selective
column coming first which is followed by most of the application
designers and database administrators. In case of the skip scan, that
rule will cause you to shoot yourself in a foot.
On 8/17/21 4:31 PM, Andy Sayer wrote:
> The mechanism is more effective when there are less distinct values of
> the first column.
>
> Hope that helps,
> Andy
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com -- http://www.freelists.org/webpage/oracle-lReceived on Wed Aug 18 2021 - 01:44:50 CEST