On Wed, Jun 24, 2020 at 3:18 AM Maciek Sakrejda <m.sakre...@gmail.com> wrote: > > On Tue, Jun 23, 2020 at 2:57 AM Amit Kapila <amit.kapil...@gmail.com> wrote: > > I don't think this is an odd situation because in this case, child > > nodes like "Nested Loop" and "Parallel Seq Scan" has a value of > > 'loops' as 3. So, to get the correct stats at those nodes, you need > > to divide it by 3 whereas, at Gather node, the value of 'loops' is 1. > > If you want to verify this thing then try with a plan where loops > > should be 1 for child nodes as well, you should get the same value at > > both Gather and Parallel Seq Scan nodes. > > Thanks for the response, but I still don't follow. I had assumed that > loops=3 was just from loops=1 for the parallel leader plus loops=1 for > each worker--is that not right? >
No, I don't think so. > I don't see any other reason for > looping over the NL node itself in this plan. The Gather itself > doesn't do any real looping, right? It is right that Gather doesn't do looping but Parallel Seq Scan node does so. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com