Re: [PATCH] Avoid unnecessary code execution in Instrument.c when TIMING is FALSE

2025-08-03 Thread torikoshia
On 2025-07-26 00:26, Hironobu SUZUKI wrote: Thanks for the proposal! Hi, Even when using EXPLAIN ANALYZE with TIMING=FALSE, the functions InstrStopNode(), InstrEndLoop(), and InstrAggNode() in Instrument.c still execute code related to the "starttime", "counter", "firsttuple", "startup", and "

Re: [PATCH] Avoid unnecessary code execution in Instrument.c when TIMING is FALSE

2025-07-26 Thread Hironobu SUZUKI
On 2025/07/26 9:29, Michael Paquier wrote: On Sat, Jul 26, 2025 at 12:26:21AM +0900, Hironobu SUZUKI wrote: Even when using EXPLAIN ANALYZE with TIMING=FALSE, the functions InstrStopNode(), InstrEndLoop(), and InstrAggNode() in Instrument.c still execute code related to the "starttime", "counter

Re: [PATCH] Avoid unnecessary code execution in Instrument.c when TIMING is FALSE

2025-07-25 Thread Michael Paquier
On Sat, Jul 26, 2025 at 12:26:21AM +0900, Hironobu SUZUKI wrote: > Even when using EXPLAIN ANALYZE with TIMING=FALSE, the functions > InstrStopNode(), InstrEndLoop(), and InstrAggNode() in Instrument.c still > execute code related to the "starttime", "counter", "firsttuple", "startup", > and "total

[PATCH] Avoid unnecessary code execution in Instrument.c when TIMING is FALSE

2025-07-25 Thread Hironobu SUZUKI
Hi, Even when using EXPLAIN ANALYZE with TIMING=FALSE, the functions InstrStopNode(), InstrEndLoop(), and InstrAggNode() in Instrument.c still execute code related to the "starttime", "counter", "firsttuple", "startup", and "total" fields within the Instrumentation structure. These operations