From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | tarkhil(at)over(dot)ru |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #13971: SysV shm is used regardless of config |
Date: | 2016-02-18 17:17:15 |
Message-ID: | CAMkU=1z-jeKx1Xe=jy=M5+RLEJwGB22ftEab_ZQpkqUPbRynQg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Feb 18, 2016 at 4:43 AM, <tarkhil(at)over(dot)ru> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13971
> Logged by: Alex Povolotsky
> Email address: tarkhil(at)over(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Ghidinelli | 2016-02-18 18:32:49 | Re: BUG #13970: Vacuum hangs on particular table; cannot be terminated - requires `kill -QUIT pid` |
Previous Message | Tom Lane | 2016-02-18 17:03:23 | Re: BUG #13972: jsonb_to_record cant map camelcase keys |