Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WxLfp-0006jB-H8 for pgsql-performance@arkaria.postgresql.org; Wed, 18 Jun 2014 19:37:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WxLfp-0000aA-1l for pgsql-performance@arkaria.postgresql.org; Wed, 18 Jun 2014 19:37:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WxLfo-0000a4-9a for pgsql-performance@postgresql.org; Wed, 18 Jun 2014 19:37:32 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WxLfl-0003NS-HX for pgsql-performance@postgresql.org; Wed, 18 Jun 2014 19:37:31 +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 s5IJbRPE027333; Wed, 18 Jun 2014 15:37:27 -0400 From: Tom Lane To: Dave Cramer cc: pgsql-performance Subject: Re: Unable to allocate 2G of shared memory on wheezy In-reply-to: References: <26671.1403118912@sss.pgh.pa.us> Comments: In-reply-to Dave Cramer message dated "Wed, 18 Jun 2014 15:24:45 -0400" Date: Wed, 18 Jun 2014 15:37:27 -0400 Message-ID: <27332.1403120247@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Dave Cramer writes: > 2014-06-18 13:37:15 EDT FATAL: could not map anonymous shared memory: > Cannot allocate memory > 2014-06-18 13:37:15 EDT HINT: This error usually means that PostgreSQL's > request for a shared memory segment exceeded available memory or swap > space. To reduce the request size (currently 8826445824 bytes), reduce > PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or > max_connections. Oh, interesting. That was the mmap that failed, so this has nothing to do with SysV shm limits. Note that your request seems to be pushing 9G, not 2G as you thought. Maybe it's just more memory than you have? regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance