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 1fgV7O-0005fM-9q for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 13:06:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fgV7M-00023Z-14 for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 13:06:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from <066ce286@free.fr>) id 1fgV7L-00023S-Q2 for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 13:06:43 +0000 Received: from smtp5-g21.free.fr ([212.27.42.5]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from <066ce286@free.fr>) id 1fgV7J-0005SX-Fw for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 13:06:43 +0000 Received: from zimbra82-e14.priv.proxad.net (unknown [172.20.243.235]) by smtp5-g21.free.fr (Postfix) with ESMTP id C83E25FFBA; Fri, 20 Jul 2018 15:06:39 +0200 (CEST) Date: Fri, 20 Jul 2018 15:06:39 +0200 (CEST) From: 066ce286@free.fr To: Alfonso Moscato Cc: pgsql-admin@lists.postgresql.org Message-ID: <1792205563.130550319.1532091999599.JavaMail.root@zimbra82-e14.priv.proxad.net> In-Reply-To: <00f101d42026$a32e17a0$e98a46e0$@merqurio.it> Subject: Re: R: repeated out of shared memory error - not related to max_locks_per_transaction MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [80.78.5.104] X-Mailer: Zimbra 7.2.0-GA2598 (ZimbraWebClient - GC67 (Win)/7.2.0-GA2598) X-Authenticated-User: 066ce286@free.fr List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk What are your values for : autovacuum_max_workers max_prepared_transactions block_size wal_block_size ? ----- Mail original ----- De: "Alfonso Moscato" =C3=80: "MichaelDBA" , "Lance' 'Campbell" Cc: pgsql-admin@lists.postgresql.org Envoy=C3=A9: Vendredi 20 Juillet 2018 14:39:01 Objet: R: repeated out of shared memory error - not related to max_locks_pe= r_transaction 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.=20 Regards=20 alfonso=20 Da: MichaelDBA =20 Inviato: venerd=C3=AC 20 luglio 2018 14:36=20 A: Campbell, Lance =20 Cc: Alfonso Moscato ; pgsql-admin@lists.postgr= esql.org=20 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 reducin= g it to see if that alleviates the problem.=20 Regards,=20 Michael Vitale=20 Campbell, Lance=20 Friday, July 20, 2018 8:32 AM=20 I would also lookup the definition of shared buffers and effective cache. I= f I remember correctly you can think of shared buffers as how much memory t= otal PostgreSQL has to work with. Effective cache is how much memory is ava= ilable 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.=20 Double check the documentation.=20 Lance=20 Sent from my iPad=20