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 1fgX6y-0003zE-Q5 for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 15:14:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fgX6w-0003HF-U3 for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jul 2018 15:14:26 +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 1fgX6w-0003H8-JT for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 15:14:26 +0000 Received: from new2-smtp.messagingengine.com ([66.111.4.224]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fgX6t-0004rM-5x for pgsql-admin@lists.postgresql.org; Fri, 20 Jul 2018 15:14:25 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id 511EF24B6; Fri, 20 Jul 2018 11:14:22 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 20 Jul 2018 11:14:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=gqd1dzl30EpG3SNTS0SA+pVhA2BHoiZyNJhGuvJdA8E=; b=t0UwXFA2 GiuiwNFsFxGLkn2WiKJZvrwgVgqlCXRd7Cdjp9Bss3zvdZhlepVm7vFLAvPKmZYz w5wucTcFoAjau4IEOTsc7G1eCUlJWJ9wV/mJDwMQ3aACF/F0b8y6LucxtJrHqe8c Q1xiRupJ7zuj/2cPff1UM/u/1ep2W+mYfCCzEj179CvZ49mK9gqW4pJXg/ENTIw/ bDvd4riDzTDZSzA+r1yFt4TpI3u0+ZbCNFVng/EDwLVYeMOPZKsYh4dsLcik81kK GAbyYSx9ZJd1UDmy2YqV9t61Osee2qVy9nouWRuT+iQQhUM+BWzIyMqIapGXY25Z auSQ4SNNk6iXAA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=gqd1dzl30EpG3SNTS0SA+pVhA2BHo iZyNJhGuvJdA8E=; b=T5qsBI4Hn8r5Y3GKaLwSa4si7oGkuJlU5lWdqbjEWV52q ednq+vSOG320mKXh3RgsmRD7QZ3Z8tSr6FM+ZgHsL9dM8EQVFdbEjqzcnt/MYZPg v1XQZZZtIqHszXsbX0hX/5ARCpyRkAdo8m/qNpMrJrgH7Qkm97lRAcoboZJ4qOvv c+UAevswVV3p4lJ5VYjh5H2TzRFEHm7YlSY6FZ3O6IpZoA+9A6gIFam8NzVaGbJ2 TiLa4du7RvTuLRoc4hedDzYvQ70LtuTcNTtwtMpfHysFiYHQQauITnmjGVHhji6S UzlDPuQ+NO6/uu47whkslN353W1R39lnTin440gpA== X-ME-Proxy: X-ME-Sender: Received: from intern.anarazel.de (c-75-69-87-158.hsd1.vt.comcast.net [75.69.87.158]) by mail.messagingengine.com (Postfix) with ESMTPA id C209310269; Fri, 20 Jul 2018 11:14:21 -0400 (EDT) Date: Fri, 20 Jul 2018 08:14:21 -0700 From: Andres Freund To: Alfonso Moscato Cc: pgsql-admin@lists.postgresql.org Subject: Re: repeated out of shared memory error - not related to max_locks_per_transaction Message-ID: <20180720151421.2coikkqwpeqghdrw@alap3.anarazel.de> References: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 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