Which predicate is NOT supported by search optimization?

• A. where timestamp1 = '2020-01-01';
• B. where timestamp1 = '2020-01-01'::date;
• C. where to_date(varchar_column) = '2020-01-01';
• D. where timestamp1 > '2020-01-02'

Answer: (C)

Predicates that use search optimization rely on direct comparisons against the stored values of a column so the optimization structure can be used to quickly filter micro-partitions. If you apply a function to a column in the predicate, like converting a varchar to a date, the optimizer can’t map that filter to the prebuilt search optimization data and must evaluate the function for every row, which eliminates the acceleration benefit. The other predicates are straightforward comparisons on the timestamp column (equality with a date literal, or a direct greater-than range), which search optimization can leverage. So, the predicate that uses a function on the column is not supported by search optimization.