RE: "actual time" in QUERY PLAN for parallel operation when loops is bigger than 1

On Wednesday, November 17, 2021 4:19 PM, Guillaume Lelarge guilla...@lelarge.info wrote: >> -> Parallel Seq Scan on c (cost=0.00..8591.67 rows=416667 width=0) (actual >> time=0.030..140.036 rows=33 loops=3) >In my previous example, actual row number is 33*

Re: "actual time" in QUERY PLAN for parallel operation when loops is bigger than 1

Hi, Le mer. 17 nov. 2021 à 06:32, tanghy.f...@fujitsu.com < tanghy.f...@fujitsu.com> a écrit : > Wednesday, November 17, 2021 6:29 AM, nikolai.berkoff < > nikolai.berk...@pm.me> wrote: > > > > Parallel query is explained in > > https://www.postgresql.org/docs/14/how-parallel-query-works.html and

RE: "actual time" in QUERY PLAN for parallel operation when loops is bigger than 1

(3) has no meaning for parallel scan node when calculate actual time? Regards, Tang > -Original Message- > From: nikolai.berkoff > Sent: Wednesday, November 17, 2021 6:29 AM > To: Tang, Haiying/唐 海英 ; > pgsql-docs@lists.postgresql.org > Subject: Re: "actual tim

Re: "actual time" in QUERY PLAN for parallel operation when loops is bigger than 1

> https://www.postgresql.org/docs/14/using-explain.html > The doc says > > "the loops value reports the total number of executions of the node, and the > > actual time and rows values shown are averages per-execution. This is done > > to make the numbers comparable with the way that the cost