Re: POC, WIP: OR-clause support for indexes
От | Alena Rybakina |
---|---|
Тема | Re: POC, WIP: OR-clause support for indexes |
Дата | |
Msg-id | 82087504-6733-42e1-b0ca-7c319c3b66b8@postgrespro.ru обсуждение исходный текст |
Ответ на | Re: POC, WIP: OR-clause support for indexes (Alexander Korotkov <aekorotkov@gmail.com>) |
Ответы |
Re: POC, WIP: OR-clause support for indexes
|
Список | pgsql-hackers |
On 23.08.2024 19:38, Alexander Korotkov wrote: > Hi, Alena! > > On Fri, Aug 23, 2024 at 5:06 PM Alena Rybakina > <a.rybakina@postgrespro.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. Sorry, I got the links mixed up. We need this link [0]. > > 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. This approach does not require a large overhead - in fact, we separately did the conversion to "any" once going through the list of restrictinfo, we form candidates in the form of boolexpr using the "and" operator, which contains "any" and "or" expression, then we check with index columns which expression suits us. -- Regards, Alena Rybakina Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
В списке pgsql-hackers по дате отправления: