Peter Eisentraut <peter.eisentr...@enterprisedb.com> writes: > 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?
I suppose it wouldn't be too hard to run into shmmni with aggressive
parallel testing; the default is just 32. But AFAIK it still works
to set the shm limits via /etc/sysctl.conf. (I wonder if you have
to disable SIP to mess with that, though.)
regards, tom lane
