Re: POC, WIP: OR-clause support for indexes
От
Andrey Lepikhov
Тема
Re: POC, WIP: OR-clause support for indexes
Дата
Msg-id
16ebc908-b486-ca16-61db-d81f943ec664@postgrespro.ru
Ответ на
Re: POC, WIP: OR-clause support for indexes (Alena Rybakina)
Список
Дерево обсуждения
Re: POC, WIP: OR-clause support for indexes Ranier Vilela <ranier.vf@gmail.com>
Re: POC, WIP: OR-clause support for indexes Tomas Vondra <tomas.vondra@enterprisedb.com>
Re: POC, WIP: OR-clause support for indexes Ranier Vilela <ranier.vf@gmail.com>
Re: POC, WIP: OR-clause support for indexes Alena Rybakina <lena.ribackina@yandex.ru>
Re: POC, WIP: OR-clause support for indexes Ranier Vilela <ranier.vf@gmail.com>
Re: POC, WIP: OR-clause support for indexes Alena Rybakina <lena.ribackina@yandex.ru>
Re: POC, WIP: OR-clause support for indexes Alena Rybakina <lena.ribackina@yandex.ru>
On 7/7/2023 15:20, Alena Rybakina wrote:
>
> because we will provide similar manipulation in this:
>
> foreach(l, gentry->consts)
> {
> Node *rexpr = (Node *) lfirst(l);
>
> rexpr = coerce_to_common_type(pstate, rexpr,
> scalar_type,
> "IN");
> aexprs = lappend(aexprs, rexpr);
> }
I'm not sure that it should be replaced.
In attachment - a bit more corrections to the patch.
The most important change - or_list contains already transformed
expression subtree. So, I think we don't need to free it at all.
--
regards,
Andrey Lepikhov
Postgres Professional
В списке pgsql-hackers по дате отправления
От: Hayato Kuroda (Fujitsu)
Дата: