| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Burd <greg(at)burd(dot)me> |
| Cc: | peter(at)eisentraut(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org, thomas(dot)munro(at)gmail(dot)com |
| Subject: | Re: Let's drop support for named POSIX semaphores |
| Date: | 2026-10-26 16:20:08 |
| Message-ID: | 639088.1793031608@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Burd <greg(at)burd(dot)me> writes:
> Peter, as to your concern that this adds another hard SysV dependency
> and so cuts against the work to let PostgreSQL run without SysV IPC (for
> macOS sandboxing): I don't think removing *named* POSIX semaphores costs
> that effort anything, because named POSIX semaphores are not the thing
> that effort would reach for.
> The non-SysV semaphore path we'd actually want is the *unnamed* kind
> (sem_init), which posix_sema.c already prefers and which backs the sem_t
> structs out of shared memory.
... and which macOS still doesn't support :-(. But moving from SysV
to named POSIX semaphores isn't realistic performance-wise, so we need
some other path altogether if we hope to address the sandboxing
problem.
> (+1 as well to Shihao's two nits, the now-unused IPCProtection macro
> and the stale runtime.sgml line about which platforms use which.)
Yeah, I noticed a few comments that need updates as well.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | g l | 2026-10-26 16:47:26 | [RFC PATCH] Skip LATERAL check in join_clause_is_movable_to() during OR-clause restriction extraction |
| Previous Message | Greg Burd | 2026-10-26 16:09:53 | Re: Hash index inserts serialise on the metapage tuple counter |