Re: [PATCH 1/1] Initial mach based shared memory support.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: James Hilliard <james(dot)hilliard1(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH 1/1] Initial mach based shared memory support.
Date: 2021-01-20 06:30:07
Message-ID: 573140.1611124207@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2021-01-20 06:34:53 Re: New IndexAM API controlling index vacuum strategies
Previous Message Michael Paquier 2021-01-20 06:29:09 Re: Odd, intermittent failure in contrib/pageinspect