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 1fgUgd-00048L-Pg for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 12:39:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fgUgb-00048q-Q0 for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 12:39:05 +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 1fgUgb-00048i-FV for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 12:39:05 +0000 Received: from smtp205-pc.aruba.it ([62.149.157.205] helo=smtpg-pc.aruba.it) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fgUgX-0001Po-Dl for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 12:39:04 +0000 Received: from DT02 ([93.63.211.242]) by smtpcm2-pc.aruba.it with bizsmtp id D0f01y00X5ELnP9010f09e; Fri, 20 Jul 2018 14:39:01 +0200 From: "Alfonso Moscato" To: "'MichaelDBA'" , "'Campbell, Lance'" Cc: References: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it> <5B51D72B.3040204@sqlexec.com> In-Reply-To: <5B51D72B.3040204@sqlexec.com> Subject: R: repeated out of shared memory error - not related to max_locks_per_transaction Date: Fri, 20 Jul 2018 14:39:01 +0200 Message-ID: <00f101d42026$a32e17a0$e98a46e0$@merqurio.it> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F2_01D42037.66B7D200" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJyTRksqbTjmmAqDGBi/OX9BtlRvgJ6PMbvAeA0gCqjON8vUA== Content-Language: it DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aruba.it; s=a1; t=1532090341; bh=USoby2IDkjvB1+g5yosXbtBsAk8d6zrlwZiVqV/bqU8=; h=From:To:Subject:Date:MIME-Version:Content-Type; b=eh3BhYy2ssobyiHbb3m8dF8OF3iI3COLMSQxShUXHIQmYUvgoOB9CbPQkw6r8mOPn hGM7f+4GQmC93a2Nwjkvb3AMDKNMZewb9l5WxNiYyYPMYk7lOABPQPaFKa1AMfkn47 n9t6KBNJhf5llcnJzbVHxqSFmwlnAUf9T4vRh9+954cIK7YcJxpIJMZH9Skj0qmRsk 0GUf6DlLe6POY0iDFF3DnRO4ppxN3rtZfkFnA++jjr1ERDge60a3YClMKwIUzHkwSo 67D0Oc6zolAXQjiC8oKLjs6dA5rKlFRSBM4hP7hthwYX/fnW72YUPwCC+WjFpnT6Ph f+u3a7fOUy1Ug== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_00F2_01D42037.66B7D200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I thought it could have be.=20 Work_mem was 131mb and I reduced it to 60mb. Errors keep starting after = one day and half. Regards alfonso =20 Da: MichaelDBA =20 Inviato: venerd=EC 20 luglio 2018 14:36 A: Campbell, Lance Cc: Alfonso Moscato ; pgsql-admin@lists.postgresql.org Oggetto: Re: repeated out of shared memory error - not related to max_locks_per_transaction =20 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 =20 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.=20 Lance Sent from my iPad =20 =20 ------=_NextPart_000_00F2_01D42037.66B7D200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I thought it could = have be.

Work_mem was 131mb = and I reduced it to 60mb. Errors keep starting after one day and = half.

Regards<= /span>

alfonso<= /span>

 

Da: MichaelDBA <MichaelDBA@sqlexec.com> =
Inviato: venerd=EC 20 luglio 2018 14:36
A: = Campbell, Lance <lance@illinois.edu>
Cc: Alfonso Moscato = <alfonso.moscato@merqurio.it>; = pgsql-admin@lists.postgresql.org
Oggetto: Re: repeated out of = shared memory error - not related to = max_locks_per_transaction

 

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

 

 

------=_NextPart_000_00F2_01D42037.66B7D200--