=?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes:
> why turn timing on increment about 26ms ?
That's the cost of reading the system clock 200000 times (once per
entry and exit to the SeqScan node). So apparently that takes about
130ns on your hardware, which is not great, but not awful either.
See
https://www.postgresql.org/message-id/flat/31856.1400021891%40sss.pgh.pa.us
for some more context.
regards, tom lane
