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 1fgXMy-00051A-NF for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 15:31:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fgXMw-000697-TI for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 15:30:58 +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 ) id 1fgXMw-000690-GF for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 15:30:58 +0000 Received: from smtp200-pc.aruba.it ([62.149.157.200] helo=smtpg-pc.aruba.it) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fgXMt-0000Lg-J4 for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 15:30:58 +0000 Received: from DT02 ([93.63.211.242]) by smtpcm2-pc.aruba.it with bizsmtp id D3Wt1y00C5ELnP9013Wt7n; Fri, 20 Jul 2018 17:30:54 +0200 From: "Alfonso Moscato" To: "'Andres Freund'" Cc: References: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it> <20180720151421.2coikkqwpeqghdrw@alap3.anarazel.de> In-Reply-To: <20180720151421.2coikkqwpeqghdrw@alap3.anarazel.de> Subject: R: repeated out of shared memory error - not related to max_locks_per_transaction Date: Fri, 20 Jul 2018 17:30:54 +0200 Message-ID: <019801d4203e$a650ee90$f2f2cbb0$@merqurio.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJyTRksqbTjmmAqDGBi/OX9BtlRvgIaFCRyo0sRLbA= Content-Language: it DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aruba.it; s=a1; t=1532100654; bh=YSOAHiyoCNbO1pVWzDz6QaZvyNHXLGuGBHdb6394b9E=; h=From:To:Subject:Date:MIME-Version:Content-Type; b=lZ2vJ/NfZ35LCRiICsM3z4pAECpnrkfFVqxW+wz/LcP4uUqZ7zafY8L4hkUU+JATI MW5iAz76fsNYzyGp7pNDJzLmfvLbrJmBsnIeKaWqHrjSx2/0hLLV874DoG5cMXH5NF wm2Vtm6vHnbw8Wo8eWeWdPjjvF8ok8NtT8TXHlD6Xd0rqwcpOTMYvLXIqyjf6W/7pd LKJmmE0pSuTdnIfrb9a2F12aGB/btblKcGMRB5nvz2v0rg5hZdr+hQiceyyYzIek/i tHAJvn4nvnzpw84Jp9/9EThrKJpPvyuDY3YxcEQKQKl9Vg0uoytplKKDlpwG+1TKM6 Zs/Tb22oXRzOw== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi andres, I said crazy beecause when it starts, there are many of them every few seconds, and the only way to stop them is to restart postgres. All of our sessions run in read_committed mode. Regards Alfonso -----Messaggio originale----- Da: Andres Freund =20 Inviato: venerd=EC 20 luglio 2018 17:14 A: Alfonso Moscato Cc: pgsql-admin@lists.postgresql.org Oggetto: Re: repeated out of shared memory error - not related to max_locks_per_transaction Hi, On 2018-07-20 13:14:53 +0200, Alfonso Moscato wrote: > We are getting crazy with "out of shared memory" errors, and we can't=20 > figure the reason. What makes them "crazy"? Could you please give the exact error message and statement it ran? Are any of your sessions running with serializable isolation? Greetings, Andres Freund