From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, gorka(dot)gil(at)openbravo(dot)com, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: remove shmmax example in Linux section |
Date: | 2017-07-31 18:58:25 |
Message-ID: | CAOR=d=0yX-_t=y6YsVWYa07Pcwvcz_GwhfLOGVDCNYvv0PR+mQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Mon, Jul 31, 2017 at 11:48 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> On 7/21/17 06:18, gorka(dot)gil(at)openbravo(dot)com wrote:
>>> In "Linux" section, show an example of setting shmmax to 16GB, when this
>>> change is not needed from pg 9.3.
>>>
>>> Maybe just remove to avoid confusion?
>>> Maybe also shmall also not needed ?
>
>> It's still needed in some cases, so I don't see why we can't have an
>> example.
>
> I wonder whether it'd make sense to recast those examples as increasing
> semaphore-related settings, as that's much more likely to be needed these
> days. I had to boost the SEMMNI setting on my workstation just last week.
> (Admittedly, I had something like a dozen postmasters going, but still,
> that was an actual change I had to make.) It'd be particularly valuable
> to document this for Linux, with its opaque "kernel.sem" API for the
> semaphore limits.
Agreed. I ran into this many years ago with multiple clusters on a box
and it is definitely non-obvious.
From | Date | Subject | |
---|---|---|---|
Next Message | sabrina.iqbal | 2017-07-31 21:13:48 | Use of term Master/Slave |
Previous Message | Tom Lane | 2017-07-31 18:48:29 | Re: remove shmmax example in Linux section |