Re: Raw parse tree is not dumped to log - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Raw parse tree is not dumped to log
Date
Msg-id 20250903.105729.896425663189147106.ishii@postgresql.org
Whole thread Raw
In response to Re: Raw parse tree is not dumped to log  (John Naylor <johncnaylorls@gmail.com>)
Responses Re: Raw parse tree is not dumped to log
List pgsql-hackers
> The individual runs have quite a bit of variation.

It's a known behavior of pgbench.

> It's good to cross check results against known facts. If my napkin
> math is right, a ~1% speedup for ~60ktps/s amounts to saving ~160ns
> per query. It's not plausible that forcing the compiler's hand for
> this branch would save several hundred clock cycles.
> 
> To be fair I tried to reproduce and found only noise-level differences:
> master: 61553
> case 1: 61423
> case 2: 61647

That's 0.3% difference, definitely noise-level. Ok, I withdraw my
claim and commit the patch without unlikely().

Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Update outdated references to SLRU ControlLock
Next
From: Peter Smith
Date:
Subject: Re: Add support for specifying tables in pg_createsubscriber.