Bas duration for a Seq scan

[Krysztophe]

See https://explain.dalibo.com/plan/G3n#plan/node/15

Computed duration :" 1s 322ms" -> there are only 9 lines in 3 blocks!

->  Seq Scan on devises  (cost=0.00..1.03 rows=3 width=11) (actual time=1322.342..1322.360 rows=3 loops=3)
                                                         Buffers: shared hit=3

[Krysztophe]

Note that the JIT was the real problem ; I'm not sure that you can detect the problem without VERBOSE

[ioguix]

Hi,

I created the same plan in verbose mode, to include JIT infos in workers: https://explain.dalibo.com/plan/9hO

JIT info related to the bad reported seqscan timing are reported there: https://explain.dalibo.com/plan/9hO#plan/node/5

Most of the subnodes produce their first row few milliseconds before the total JIT timing, and a few are producing rows immediately: (see https://explain.dalibo.com/plan/9hO#plan/node/13). I'm not sure how to link JIT timing with actual node timing...