Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not?
От | Ian Lawrence Barwick |
---|---|
Тема | Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not? |
Дата | |
Msg-id | CAB8KJ=gSqwM1Lo+CP++5+PAfYu+Gajzp4HWEvd_azNHCocQBaw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not? (Andrey Lepikhov <a.lepikhov@postgrespro.ru>) |
Ответы |
Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not?
|
Список | pgsql-hackers |
2022年7月7日(木) 20:11 Andrey Lepikhov <a.lepikhov@postgrespro.ru>: > > On 17/5/2022 05:00, Andy Fan wrote: > > Thanks. But I will wait to see if anyone will show interest with this. > > Or else > > Moving alone is not a great experience. > To move forward I've rebased your patchset onto new master, removed > annoying tailing backspaces and applied two regression test changes, > caused by second patch: first of changes are legal, second looks normal > but should be checked on optimality. > As I see, a consensus should be found for the questions: > 1. Case of redundant clauses (x < 100 and x < 1000) > 2. Planning time degradation for trivial OLTP queries Hi cfbot reports the patch no longer applies [1]. As CommitFest 2022-11 is currently underway, this would be an excellent time to update the patch. [1] http://cfbot.cputube.org/patch_40_3524.log Thanks Ian Barwick
В списке pgsql-hackers по дате отправления: