pgsql: Handle EACCES errors from kevent() better.

From: Thomas Munro <tmunro(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Handle EACCES errors from kevent() better.
Date: 2020-10-15 05:40:34
Message-ID: E1kSw0A-0006dZ-1j@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Handle EACCES errors from kevent() better.

While registering for postmaster exit events, we have to handle a couple
of edge cases where the postmaster is already gone. Commit 815c2f09
missed one: EACCES must surely imply that PostmasterPid no longer
belongs to our postmaster process (or alternatively an unexpected
permissions model has been imposed on us). Like ESRCH, this should be
treated as a WL_POSTMASTER_DEATH event, rather than being raised with
ereport().

No known problems reported in the wild. Per code review from Tom Lane.
Back-patch to 13.

Reported-by: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Discussion: https://postgr.es/m/3624029.1602701929%40sss.pgh.pa.us

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/47522ee00ddbe77280e4c063605b443ec1de3881

Modified Files
--------------
src/backend/storage/ipc/latch.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Kapila 2020-10-15 07:07:04 Re: pgsql: Restore replication protocol's duplicate command tags
Previous Message Thomas Munro 2020-10-15 05:40:20 pgsql: Handle EACCES errors from kevent() better.