Subject: Re: How should the correct value of shmmax be calculated for DWH
 (OLAP) server
To: Laurenz Albe <laurenz.albe@cybertec.at>,
 "Shukla, Sumeet" <ShuklaSu@advisory.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
References: <BBF9115E-9E39-4710-B9EF-AE41EF576F38@advisory.com>
 <4647b0c67c2c5d4dc08032f1b11240665711af95.camel@cybertec.at>
From: "Gunnar \"Nick\" Bluth" <gunnar.bluth@pro-open.de>
Message-ID: <5BC4466E.7070902@pro-open.de>
Date: Mon, 15 Oct 2018 09:49:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <4647b0c67c2c5d4dc08032f1b11240665711af95.camel@cybertec.at>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="N8ddfk00oCpsoTagOn3UKv6nioq2kdHhs"
Precedence: bulk

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--N8ddfk00oCpsoTagOn3UKv6nioq2kdHhs
Content-Type: multipart/mixed; boundary="wIJojdWKfRsPPIQA98xV3MwS4dV8919vT";
 protected-headers="v1"
From: "Gunnar \"Nick\" Bluth" <gunnar.bluth@pro-open.de>
To: Laurenz Albe <laurenz.albe@cybertec.at>,
 "Shukla, Sumeet" <ShuklaSu@advisory.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Message-ID: <5BC4466E.7070902@pro-open.de>
Subject: Re: How should the correct value of shmmax be calculated for DWH
 (OLAP) server
References: <BBF9115E-9E39-4710-B9EF-AE41EF576F38@advisory.com>
 <4647b0c67c2c5d4dc08032f1b11240665711af95.camel@cybertec.at>
In-Reply-To: <4647b0c67c2c5d4dc08032f1b11240665711af95.camel@cybertec.at>

--wIJojdWKfRsPPIQA98xV3MwS4dV8919vT
Content-Type: multipart/mixed;
 boundary="------------010507040302050805040404"

This is a multi-part message in MIME format.
--------------010507040302050805040404
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Am 15.10.2018 um 09:43 schrieb Laurenz Albe:
> Shukla, Sumeet wrote:
>> Can someone please help me determine the appropriate value of kernel s=
hmmax
>> parameter for PostgreSQL configured for Data Warehouse use?
>=20
> Simple. Set it to anything bigger than your "shared_buffers" setting.
> If PostgreSQL manages to start, your setting is big enough.
>=20

As a matter of fact, you shouldn't need to set SHMMAX anyway, unless you
tampered with "dynamic_shared_memory_type" or you are on a very exotic
OS ;-)

Best regards,
--=20
Gunnar "Nick" Bluth
RHCE/SCLA

Mobil +49 172 8853339
Email: gunnar.bluth@pro-open.de
_____________________________________________________________
In 1984 mainstream users were choosing VMS over UNIX.
Ten years later they are choosing Windows over UNIX.
What part of that message aren't you getting? - Tom Payne


--------------010507040302050805040404
Content-Type: application/pgp-keys;
 name="0x3289338C.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="0x3289338C.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.22 (MingW32)

mQENBFOuo7ABCADU3rFM4gBv4l/Xjfry27pfdYgvWrcR1RA/vLfOgjqivSbMQEHH
bTWprJRjB2EbzmTS+faSa/V+mH/jIKBytCc5+hprBd/m5if3/v2PKA7+MHsy1H9T
7FqTKRccNl7RIcKFOaonIbY4qMyH6cFafZOgqaGlc3ibfX7PiCL+mdl1mPoyWeVR
sKoddSobI40noE+se/FrnKZRDRWqqx7zvTRRK9vKUVDFM+Y3Kg3EDL3Qmt3MocM7
FtBZDaeyFZiKdf7bNaWM977aGwiA1gQQp+/TmB1qqSyOTzbPhxfr7G9vWdbVS2ph
80RSrxI/sF3LUNeJtTjB/jtKiG49arBqC1eDABEBAAG0Lkd1bm5hciAiTmljayIg
Qmx1dGggPGd1bm5hci5ibHV0aEBwcm8tb3Blbi5kZT6JAT8EEwECACkFAlOuo7AC
GyMFCQlmAYAHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRAQEK5rMokzjLin
CACaTXqjA7Qc6lpljpz3/5SpmPlvEDdX5mR76jN8326qkSQw7i8WBGW/5NO669OY
4ITlLbu/XL11x6hzCh7ZxMJo3fSYN+fh1tfEnNGw0NjUoy1JdBB+2B3beY+0LEBG
ZMm56HZC1u4qZq2drLM+sZIi6f8ML0NCh41s01SeX6hGQ609zCcFRNNk98pXOBER
a2kDi9wn1UvK1tECxCXuiO6HhPzhme/nFAxoBdBdATCl5EEnnLD+JfhSr2LShgXu
LQxJA6odvggfDVlS913rb0zDtV6s+6bfR+qmD4igBgC6Xl8ceDJpbS4ER7Uvw78n
Sa2i3Yub28FAGr+RvpFLi9PruQENBFOuo7ABCAC6E2x7GZ1LrIQMlNr2XYvCG9DB
p181PJJ95w4BwuaKmFBDHc5tE7p5S2sNfNfYNUjDzpr47lU5+85Ffqtf27gV8Ftd
rqv/d2lbH9+w6wShB9QOy11gPPdkB62o9CKwk+XInN2DJITWsgI8hk6NNzbotD27
x7x4fxQxBUE6YkHnJMziqwZ5emLFP0A2XPIDK6tw87UZNOnEaJ9kP3WOKihNOtMq
mr7+4BQQCyfj13k32219UZglnHtYaGuNmXOc0KHoFEIA2pkgeXRQShrwz4gdCaSN
FUZPAVeeWmdqAmnKKb+Sk7czft/wdtmBD0BykYRoZxQ3JlkHG7oH7wGXmi1TABEB
AAGJASUEGAECAA8FAlOuo7ACGwwFCQlmAYAACgkQEBCuazKJM4xN1wf+MPLXrQ10
LBRtYjD16LsvxDyEcSMoWGc26DO/TDsGwme2NVfL0JufExgdpvkk/x4wzBwdkYfF
dNKU3CyA+3T4FuKGL7RPrICJa+VdCvwMk8dzLqF0UgdfVHtCnUQoQmNnDD7gODw/
GTIKpWw+iEE2/EANAONXj7EC+VsW895/C5aQEZx++cSonrHFSSIUp1OGJoVlmFnJ
MFCTTElmayTcmfOwGHrn97Et5YePMOsyqWZas+URuJveoTdGhDToOIufECGb3WJa
J8rFL+ni3NKoiZhZMYVQ+XC8f64Mi5kXlfsylVu6kgCoFqnq7FTpwqOiRml4APeX
GBC6uZW6fUGNDQ=3D=3D
=3D//tm
-----END PGP PUBLIC KEY BLOCK-----

--------------010507040302050805040404--

--wIJojdWKfRsPPIQA98xV3MwS4dV8919vT--

--N8ddfk00oCpsoTagOn3UKv6nioq2kdHhs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJbxEZ7AAoJEBAQrmsyiTOMIpEH/0YWa8K94bwgONZfQ9KJsLwR
Rh/Vpzc45JFYdrlsKcz9Kx0rr+4njPs3rM1COZC0dmvBPQWXuessyWRA4uOaehwo
A7Wc/CJAK2glCeNWBKje+5/rCha79oSsq3RuA+J94okaRK5Dgu6KNbWjtmg/dCTk
D0SDmsGDG6hrhNxI4GQoo2V8/Tre3uyIinYAYyJh2NAYhN+oIkzafjaqJAimSdEI
1Gc9RJNH2MTt0WYG1wJdYt6kEF+0LaLZTYL5pZ4b8EWugcpCNvcthpeMBqMTFTSb
Ata5uwV5dpUrvPy+2ve9n1qUZDVTm4G0b0sKAt6Eesm71C0f+WHhs5QmDUYr0bE=
=TAX/
-----END PGP SIGNATURE-----

--N8ddfk00oCpsoTagOn3UKv6nioq2kdHhs--