Hi,
On 2/28/23 4:30 PM, Bharath Rupireddy wrote:
> Hi,
>
> Most of the multiplexed SIGUSR1 handlers are setting latch explicitly
> when the procsignal_sigusr1_handler() can do that for them at the end.
Right.
> These multiplexed handlers are currently being used as SIGUSR1
> handlers, not as independent handlers, so no problem if SetLatch() is
> removed from them.
Agree, they are only used in procsignal_sigusr1_handler().
> A few others do it right by saying /* latch will be
> set by procsignal_sigusr1_handler */.
Yeap, so do HandleProcSignalBarrierInterrupt() and HandleLogMemoryContextInterrupt().
> Although, calling SetLatch() in
> quick succession does no harm (it just returns if the latch was
> previously set), it seems unnecessary.
>
Agree.
> I'm attaching a patch that avoids multiple SetLatch() calls.
>
> Thoughts?
>
I agree with the idea behind the patch. The thing
that worry me a bit is that the changed functions are defined
as external and so may produce an impact outside of core pg and I'm
not sure that's worth it.
Otherwise the patch LGTM.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
