Re: POC, WIP: OR-clause support for indexes
От | Alexander Korotkov |
---|---|
Тема | Re: POC, WIP: OR-clause support for indexes |
Дата | |
Msg-id | CAPpHfdu71LCrXfwaRot1u_xfx7r92VFvZNRLvQJS79B3XFmBhg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: POC, WIP: OR-clause support for indexes (Alena Rybakina <a.rybakina@postgrespro.ru>) |
Ответы |
Re: POC, WIP: OR-clause support for indexes
Re: POC, WIP: OR-clause support for indexes Re: POC, WIP: OR-clause support for indexes |
Список | pgsql-hackers |
Hi! On Mon, Mar 24, 2025 at 2:46 PM Alena Rybakina <a.rybakina@postgrespro.ru> wrote: > I agree with Andrey's changes and think we should fix this, because otherwise it might be inconvenient. > For example, without this changes we will have to have different test output files for the same query for different versionsof Postres in extensions if the whole change is only related to the order of column output for a transformation thatwas not applied. I agree with problem spotted by Andrei: it should be preferred to preserve original order of clauses as much as possible. The approach implemented in Andrei's patch seems fragile for me. Original order is preserved if we didn't find any group. But once we find a single group original order might be destroyed completely. The attached patch changes the reordering algorithm of group_similar_or_args() in the following way. We reorder each group of similar clauses so that the first item of the group stays in place, but all the other items are moved after it. So, if there are no similar clauses, the order of clauses stays the same. When there are some groups, only required reordering happens while the rest of the clauses remain in their places. ------ Regards, Alexander Korotkov Supabase
Вложения
В списке pgsql-hackers по дате отправления: