Re: BUG #17618: unnecessary filter column <> text even after adding index

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, sindysenorita(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17618: unnecessary filter column <> text even after adding index
Date: 2022-09-24 00:06:06
Message-ID: CAMbWs4878nvTT=D6eECLRJqrz3+FifKr6XRSonrP0pyqmSVCLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Sep 23, 2022 at 9:29 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:

> So I think we need to run eval_const_expressions on indexquals before we
> check for duplicate clauses, something like attached.
>

BTW, (revise to the v1 patch), if this is the right way to go, we should
do that before the foreach loop, so that we need to run
eval_const_expressions on indexquals only once rather than for each scan
clause.

Thanks
Richard

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2022-09-24 00:10:41 Re: BUG #17619: AllocSizeIsValid violation in parallel hash join
Previous Message Tom Lane 2022-09-24 00:04:51 Re: BUG #17618: unnecessary filter column <> text even after adding index