Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eEheM-0004yc-AX for pgsql-admin@arkaria.postgresql.org; Tue, 14 Nov 2017 20:17:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1eEheL-0004PM-Iv for pgsql-admin@arkaria.postgresql.org; Tue, 14 Nov 2017 20:17:37 +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.84_2) (envelope-from ) id 1eEhcR-0000yg-KN for pgsql-admin@postgresql.org; Tue, 14 Nov 2017 20:15:39 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eEhcK-00042p-It for pgsql-admin@postgresql.org; Tue, 14 Nov 2017 20:15:38 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id vAEKFTuJ019653; Tue, 14 Nov 2017 15:15:29 -0500 From: Tom Lane To: Arjun Ranade cc: Alvaro Aguayo Garcia-Rada , pgsql-admin Subject: Re: PG10 - Out of shared memory / invalid memory alloc request size In-reply-to: References: <1623340727.404090.1510689186227.JavaMail.zimbra@opensysperu.com> <1284888832.404212.1510689919110.JavaMail.zimbra@opensysperu.com> Comments: In-reply-to Arjun Ranade message dated "Tue, 14 Nov 2017 15:07:18 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19651.1510690529.1@sss.pgh.pa.us> Date: Tue, 14 Nov 2017 15:15:29 -0500 Message-ID: <19652.1510690529@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Arjun Ranade writes: > We will try that. I am wondering why we need to worry about this in pg10 > whereas we had no issues with shared memory in 9.4 What it looks like to me is something is miscomputing a memory request size and asking for some silly amount of memory. I think you're dealing with a software bug, not inadequate configuration. > Anecdotally it seems that these errors are happening when > powa_take_snapshot() (Postgres workload analyzer) is running as well but > I can't confirm that. The first theory that comes to mind is that powa_take_snapshot() requires some updates for PG10. I do not know what that function is or where you got it from, but if there's any C code involved, you need to discuss this with its developer(s). regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin