Re: BUG #17618: unnecessary filter column <> text even after adding index - Mailing list pgsql-bugs

From Richard Guo
Subject Re: BUG #17618: unnecessary filter column <> text even after adding index
Date
Msg-id CAMbWs49oBk4EfHC+44xkuAwQYnGH5pyKP40=FwZv9Zecx9=3Mg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17618: unnecessary filter column <> text even after adding index  (Richard Guo <guofenglinux@gmail.com>)
Responses Re: BUG #17618: unnecessary filter column <> text even after adding index  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs

On Mon, Sep 26, 2022 at 7:42 PM Richard Guo <guofenglinux@gmail.com> wrote:
On Sat, Sep 24, 2022 at 8:41 AM Richard Guo <guofenglinux@gmail.com> wrote:
Yeah, I agree that running eval_const_expressions here is expensive.
Maybe we can just do the reverse transformation in
create_bitmap_scan_plan against what we do for boolean index in
match_boolean_index_clause?
 
Following this idea, I come up with v2 patch. Is this the right
direction to go?
 
Update with v3 patch, nothing changes except fixes a test failure
spotted by cfbot.

Thanks
Richard
Attachment

pgsql-bugs by date:

Previous
From: Amit Kapila
Date:
Subject: Re: BUG #17670: Logical Replication data may be lost on the subscription under certain scenarios
Next
From: Mike Burgener
Date:
Subject: AW: BUG #17672: Wrong logic of Postgresql Resporitory Naming and mirroring incompatibility