pgsql: Explain postmaster's treatment of SIGURG.

From: Thomas Munro <tmunro(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Explain postmaster's treatment of SIGURG.
Date: 2021-04-18 22:38:30
Message-ID: E1lYG3i-0004rw-H9@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Explain postmaster's treatment of SIGURG.

Add a few words of comment to explain why SIGURG doesn't follow the
dummy_handler pattern used for SIGUSR2, since that might otherwise
appear to be a bug.

Discussion: https://postgr.es/m/4006115.1618577212%40sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/8e861eaae86eeaf5589963c9b1c7ce6d4c2acbb5

Modified Files
--------------
src/backend/postmaster/postmaster.c | 5 +++++
1 file changed, 5 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2021-04-18 23:36:44 Re: pgsql: Use SIGURG rather than SIGUSR1 for latches.
Previous Message Peter Eisentraut 2021-04-18 14:12:54 pgsql: Add missing source files to nls.mk