| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: kevent latch paths don't handle postmaster death well |
| Date: | 2020-10-15 21:40:51 |
| Message-ID: | 3896447.1602798051@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> I couldn't resist digging further into the Apple sources to figure out
> what was going on there, and I realised that the code path I was
> looking at can only report EACCES if you asked for NOTE_EXITSTATUS,
> which appears to be an Apple extension to the original FreeBSD kqueue
> system designed to let you receive the exit status of the monitored
> process. That is indeed much more privileged information, and it's
> only allowed for your own children.
Ah.
> So it's possible that commit
> 70516a17 was a waste of electrons, but I don't think it can hurt;
Yeah, I'm not inclined to revert it. If we did get that errno,
it'd be hard to interpret it in any way that didn't involve the
postmaster being gone.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2020-10-15 22:11:34 | Re: stress test for parallel workers |
| Previous Message | Thomas Munro | 2020-10-15 21:32:54 | Re: kevent latch paths don't handle postmaster death well |