From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: gorka.gil@openbravo.com
Cc: pgsql-docs@postgresql.org
Subject: Re: remove shmmax example in Linux section
Date: Mon, 31 Jul 2017 14:48:29 -0400
Message-ID: <8627.1501526909@sss.pgh.pa.us> (raw)
In-Reply-To: <88dc6648-0d61-dc18-e547-f16f1c69ebf5@2ndquadrant.com>
References: <20170721101823.19353.86968@wrigleys.postgresql.org>
<88dc6648-0d61-dc18-e547-f16f1c69ebf5@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 7/21/17 06:18, gorka.gil@openbravo.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.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com, gorka.gil@openbravo.com
Subject: Re: remove shmmax example in Linux section
In-Reply-To: <8627.1501526909@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox