From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
cc: gorka.gil@openbravo.com, pgsql-docs@postgresql.org
Subject: Re: remove shmmax example in Linux section
In-reply-to: <88dc6648-0d61-dc18-e547-f16f1c69ebf5@2ndquadrant.com>
References: <20170721101823.19353.86968@wrigleys.postgresql.org>
 <88dc6648-0d61-dc18-e547-f16f1c69ebf5@2ndquadrant.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
	message dated "Mon, 31 Jul 2017 14:32:43 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8626.1501526909.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 31 Jul 2017 14:48:29 -0400
Message-ID: <8627.1501526909@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 7/21/17 06:18, gorka.gil@openbravo.com wrote:
>> In &quot;Linux&quot; section, show an example of setting shmmax to 16GB,=
 when this
>> change is not needed from pg 9.3.
>>=20
>> 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


--=20
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs