Re: Optimising latch signals

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Optimising latch signals
Date: 2021-02-26 11:04:55
Message-ID: CA+hUKGJjScGSty28MPFXbBxtEcVigDonupK_NAXpoFtjAkgFyQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here's a new version with two small changes from Andres:
1. Reorder InitPostmasterChild() slightly to avoid hanging on
EXEC_BACKEND builds.
2. Revert v2's use of raise(x) instead of kill(MyProcPid, x); glibc
manages to generate 5 syscalls for raise().

I'm planning to commit this soon if there are no objections.

Attachment Content-Type Size
v5-0001-Optimize-latches-to-send-fewer-signals.patch text/x-patch 2.7 KB
v5-0002-Use-SIGURG-rather-than-SIGUSR1-for-latches.patch text/x-patch 7.7 KB
v5-0003-Use-signalfd-for-epoll-latches.patch text/x-patch 13.2 KB
v5-0004-Use-EVFILT_SIGNAL-for-kqueue-latches.patch text/x-patch 5.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2021-02-26 11:14:18 Re: non-HOT update not looking at FSM for large tuple update
Previous Message Amit Kapila 2021-02-26 10:58:26 Re: [HACKERS] logical decoding of two-phase transactions