On 2020-11-22 09:19, James Hilliard wrote:
> OSX implements sysv shmem support via a mach wrapper, however the mach
> sysv shmem wrapper has some severe restrictions that prevent us from
> allocating enough memory segments in some cases.
>
> These limits appear to be due to the way the wrapper itself is
> implemented and not mach.
>
> For example when running a test suite that spins up many postgres
> instances I commonly see this issue:
> DETAIL: Failed system call was shmget(key=5432002, size=56, 03600).
This is the first I've heard in years of shared memory limits being a
problem on macOS. What settings or what levels of concurrency do you
use to provoke these errors?