Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fgUdz-00041c-HM for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 12:36:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fgUdx-0003u5-Kd for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 12:36:21 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fgUdx-0003ty-9t for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 12:36:21 +0000 Received: from mout.perfora.net ([74.208.4.196]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fgUdu-0001Oi-Mf for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 12:36:20 +0000 Received: from [192.168.1.101] ([98.169.215.140]) by mrelay.perfora.net (mreueus002 [74.208.5.2]) with ESMTPSA (Nemesis) id 0LyCBP-1g37gL1gHt-015byb; Fri, 20 Jul 2018 14:36:00 +0200 Message-ID: <5B51D72B.3040204@sqlexec.com> Date: Fri, 20 Jul 2018 08:35:55 -0400 From: MichaelDBA User-Agent: Postbox 5.0.25 (Windows/20180328) MIME-Version: 1.0 To: "Campbell, Lance" CC: Alfonso Moscato , "pgsql-admin@lists.postgresql.org" Subject: Re: repeated out of shared memory error - not related to max_locks_per_transaction References: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it> In-Reply-To: Content-Type: multipart/alternative; boundary="------------000501010803000406020504" X-Provags-ID: V03:K1:5wzWSsmwIwYYcMhWiD8lPfd2CCZN2SUo1KO79gClbzpSgFpI7rw TonPkN+EHX59sUCAEQaXvO0XNK7HVjIGSw9hzLy1wSeRIWtwMX1dST66v+D4LbV11EOHTRS kVmr5Kpo4QlH2rwFHcPIvt1YVps58Xvz5o/+zkdmC+Zos1KGD6i6YgLfshTXpw6vxcGAQGd ub+2vbTVOfiYLNiGpHdkQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:hzC2jEQV/zE=:7RNQQlHrVZyYdjKhW9+hBz Hvobt5JGh2/EjnfkeB7XUa1fObG9LlpXKILf2cdff10ZUuNs1eTM/d7HZ0f9WkWQaJ97O/X1P xA6Sd/7Np48Dz1svfjaU/wGWpPiwb7eB3fNzd5mYeIMYwroajbmzl+eSoUfSJoZJoMAyAgq7q gnsKVGeMmzIZI0lE5X521difTqDnGhfaCdKsp27OogDanOdwcQbRUd2LMT/3zCeiM76WBF91S BD1CVPPhRuvG1b+DF+jWpOf+7kuKfynFkoVO7AD0jo2f6oUglrl6wvYuGonyVsgeZ+RvM7+rd pWwCczPiJi4M0umCYKFXqv90fYceMmFLRwJe8CxSI5F2egnCD0kIDe94Zx5KkI+x5NyUP3xmq /KWiQbw2K5ciUhFQhoozidJifhnDcFJ0MVvLimLLPCsurmy+qZFvg+qRK1sJt2OTNsHAOY7xo MMRkeloZuNXjLmP5DCMezsGQQr4Vxeii1o2UBHLj250XBFrFJrY9iDHCaHZU7xUshZdbf/3he mpEqP/2dk0l+OJfNoOgkAJeHv1sEFzllHfvPmgIlTMea1c0dpAXgM0qUqqXCE63ES+DvHaTrx dq+ZU6jhdJCv6FxgSYMvpZh65r9sYVhq7ZJ48nFddlyFEyvErxAJ4DAqmdDG1EWMWmfTIhxfN A/uVSCC6vXlekcPYc3ci1fTWF3hR2XRdd+pwU6n6IpfZDgXWoJBRiYReFDnW/rQZANRol/DPT bKeVP3lX7nr/fGhZ List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------000501010803000406020504 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Perhaps your "work_mem" setting is causing the memory problems. Try reducing it to see if that alleviates the problem. Regards, Michael Vitale > Campbell, Lance > Friday, July 20, 2018 8:32 AM > I would also lookup the definition of shared buffers and effective > cache. If I remember correctly you can think of shared buffers as how > much memory total PostgreSQL has to work with. Effective cache is how > much memory is available for PostgreSQL to run, shared buffers, as > well as an estimate of how much memory is available to the OS to cache > files in memory. So effective cache should be equal to or larger than > shared buffers. Effective cache is used to help with the SQL planning. > > Double check the documentation. > > Lance > > Sent from my iPad > > --------------000501010803000406020504 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Perhaps your "work_mem" setting is causing the memory problems.  Try reducing it to see if that alleviates the problem.

Regards,
Michael Vitale

Friday, July 20, 2018 8:32 AM
I would also lookup the definition of shared buffers and effective cache. If I remember correctly you can think of shared buffers as how much memory total PostgreSQL has to work with. Effective cache is how much memory is available for PostgreSQL to run, shared buffers, as well as an estimate of how much memory is available to the OS to cache files in memory. So effective cache should be equal to or larger than shared buffers. Effective cache is used to help with the SQL planning.

Double check the documentation.

Lance

Sent from my iPad



--------------000501010803000406020504--