Re: BUG #15268: Documentation surrounding sysvipc configuration and isolation is out-of-date as of FreeBSD 11

On Sun, Jul 8, 2018 at 9:50 PM, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15268
> Logged by: D. Ebdrup
> Email address: debdrup(at)gmail(dot)com
> PostgreSQL version: 10.0
> Operating system: FreeBSD
> Description:
>
> Owing to some rather big changes in FreeBSD, the steps recommended in the
> documentation for all supported (and unsupported) versions of pgsql on
> FreeBSD 11 and future versions regarding sysvipc are no longer accurate.
> Notably, the security.jail.sysvipc_allowed sysctl has been marked deprecated
> (ie. to be removed in a future version) and the sysvmsg, sysvsem, and
> sysvshm properties for jails have been added which can function like
> security.jail.sysvipc_allowed/allow.sysvipc used to work, in addition to
> which a value named "new" has been added which offers proper per-jail
> isolation of SysV messages, semaphores and shadow memory.
> This can be confirmed by going to https://man.freebsd.org/jail(8) and
> searching for the second result of sysvmsg as a text-search.

Right, thanks for the report. Any chance you could propose some new
wording for that paragraph, or a patch for doc/src/sgml/runtime.sgml?

--
Thomas Munro
http://www.enterprisedb.com