Re: POC, WIP: OR-clause support for indexes
От | Andrei Lepikhov |
---|---|
Тема | Re: POC, WIP: OR-clause support for indexes |
Дата | |
Msg-id | 5f119769-ab11-4807-abcc-71d5dd914ea0@postgrespro.ru обсуждение исходный текст |
Ответ на | Re: POC, WIP: OR-clause support for indexes (jian he <jian.universality@gmail.com>) |
Ответы |
Re: POC, WIP: OR-clause support for indexes
|
Список | pgsql-hackers |
On 16/2/2024 07:00, jian he wrote: > On Wed, Feb 14, 2024 at 11:21 AM Andrei Lepikhov > <a.lepikhov@postgrespro.ru> wrote: > My OS: Ubuntu 22.04.3 LTS > I already set the max_parallel_workers_per_gather to 10. > So for all cases, it should use parallelism first? > > a better question would be: > how to make the number of OR less than 29 still faster when > enable_or_transformation is ON by only set parameters? In my test environment this example gives some subtle supremacy to ORs over ANY with only 3 ors and less. Please, provide next EXPLAIN ANALYZE results for the case you want to discuss here: 1. with enable_or_transformation enabled 2. with enable_or_transformation disabled 3. with enable_or_transformation disabled but with manual transformation OR -> ANY done, to check the overhead of this optimization. -- regards, Andrei Lepikhov Postgres Professional
В списке pgsql-hackers по дате отправления: