| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | James Coleman <jtc331(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Geoghegan <pg(at)bowt(dot)ie>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Binary search in ScalarArrayOpExpr for OR'd constant arrays |
| Date: | 2021-05-08 04:50:00 |
| Message-ID: | CAApHDvoYszhqBYtBnE-SR_+rXTqnhQyxE2FXPOEi3LiNYPJBPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 8 May 2021 at 14:04, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> I'm not opposed to adding some new field if that's what it takes. I'd
> imagine the new field will be something like negfuncid which will be
> InvalidOid unless the hash function is set and useOr == false
Just while this is still swapped into main memory, I've attached a
patch that adds a new field to ScalarArrayOpExpr rather than
repurposing the existing field.
David
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Speedup-NOT-IN-with-a-set-of-Consts.patch | application/octet-stream | 20.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2021-05-08 04:57:54 | Re: Anti-critical-section assertion failure in mcxt.c reached by walsender |
| Previous Message | houzj.fnst@fujitsu.com | 2021-05-08 03:38:51 | Inaccurate error message when set fdw batch_size to 0 |