Re: Wired if-statement in gen_partprune_steps_internal
От | Amit Langote |
---|---|
Тема | Re: Wired if-statement in gen_partprune_steps_internal |
Дата | |
Msg-id | CA+HiwqFCKm9krnke1b8+M5z9dnam=vD4oxDPHe1qJLO-rLahcg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Wired if-statement in gen_partprune_steps_internal (David Rowley <dgrowleyml@gmail.com>) |
Ответы |
Re: Wired if-statement in gen_partprune_steps_internal
|
Список | pgsql-hackers |
On Thu, Apr 8, 2021 at 7:41 PM David Rowley <dgrowleyml@gmail.com> wrote: > On Thu, 8 Apr 2021 at 21:04, Amit Langote <amitlangote09@gmail.com> wrote: > > Maybe, we should also updated the description of node struct as > > follows to consider that last point: >> > > * PartitionPruneStepOp - Information to prune using a set of mutually ANDed > > * OpExpr and any IS [ NOT ] NULL clauses > > I didn't add that. I wasn't really sure if I understood why we'd talk > about PartitionPruneStepCombine in the PartitionPruneStepOp. I thought > the overview in gen_partprune_steps_internal was ok to link the two > together and explain why they're both needed. Sorry, maybe the way I wrote it was a bit confusing, but I meant to suggest that we do what I have quoted above from my last email. That is, we should clarify in the description of PartitionPruneStepOp that it contains information derived from OpExprs and in some cases also IS [ NOT ] NULL clauses. Thanks for the commit. -- Amit Langote EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: