Re: BUG #13971: SysV shm is used regardless of config - Mailing list pgsql-bugs

From Jeff Janes
Subject Re: BUG #13971: SysV shm is used regardless of config
Date
Msg-id CAMkU=1z-jeKx1Xe=jy=M5+RLEJwGB22ftEab_ZQpkqUPbRynQg@mail.gmail.com
Whole thread Raw
In response to BUG #13971: SysV shm is used regardless of config  (tarkhil@over.ru)
List pgsql-bugs
On Thu, Feb 18, 2016 at 4:43 AM,  <tarkhil@over.ru> wrote:
> The following bug has been logged on the website:
>
> Bug reference:      13971
> Logged by:          Alex Povolotsky
> Email address:      tarkhil@over.ru
> PostgreSQL version: 9.4.6
> Operating system:   FreeBSD 10.2
> Description:
>
> regardless of dynamic_shared_memory_type, postgres upon start still calls
> shmget.

That setting controls what kind of memory is used by custom dynamic
Background Worker Processes.  It is not the only shared memory used by
PostgreSQL--in fact most people don't use that kind at all because
most people don't use custom dynamic background worker processes.


> In FreeBSD's jail, with disabled sysvipc, it yields error in
> src/backend/port/pg_shmem.c

You can't do that.  sysvipc is not optional.

Cheers,

Jeff

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #13972: jsonb_to_record cant map camelcase keys
Next
From: Brian Ghidinelli
Date:
Subject: Re: BUG #13970: Vacuum hangs on particular table; cannot be terminated - requires `kill -QUIT pid`