| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru> |
| Cc: | Andrei Lepikhov <lepihov(at)gmail(dot)com>, Nikolay Shaplov <dhyan(at)nataraj(dot)su>, pgsql-hackers(at)lists(dot)postgresql(dot)org, jian he <jian(dot)universality(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, teodor(at)sigaev(dot)ru, Peter Eisentraut <peter(at)eisentraut(dot)org>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
| Subject: | Re: POC, WIP: OR-clause support for indexes |
| Date: | 2024-08-23 16:38:36 |
| Message-ID: | CAPpHfdtdeEJY_joo-arg8G8kzxS7CQ1_E1dPf+0QV0RnWXZO8g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi, Alena!
On Fri, Aug 23, 2024 at 5:06 PM Alena Rybakina
<a(dot)rybakina(at)postgrespro(dot)ru> wrote:
> To be fair, I fixed this before [0] by selecting the appropriate group
> of "or" expressions to transform them to "ANY" expression and then
> checking for compatibility with the index column. maybe we should try
> this too? I can think about it.
>
> [0]
> https://www.postgresql.org/message-id/531fc0ab-371e-4235-97e3-dd2d077b6995%40postgrespro.ru
I probably didn't get your message. Which patch version you think
resolve the problem? I see [0] doesn't contain any patch.
I think further progress in this area of grouping OR args is possible
if there is a solution, which doesn't take extraordinary computational
complexity.
------
Regards,
Alexander Korotkov
Supabase
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-08-23 17:11:45 | Re: On disable_cost |
| Previous Message | Jacob Champion | 2024-08-23 16:25:12 | Re: PG_TEST_EXTRA and meson |