Re: Unable to allocate 2G of shared memory on wheezy - Mailing list pgsql-performance

From Tom Lane
Subject Re: Unable to allocate 2G of shared memory on wheezy
Date
Msg-id 27332.1403120247@sss.pgh.pa.us
Whole thread Raw
In response to Re: Unable to allocate 2G of shared memory on wheezy  (Dave Cramer <davecramer@gmail.com>)
List pgsql-performance
Dave Cramer <davecramer@gmail.com> 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


pgsql-performance by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Unable to allocate 2G of shared memory on wheezy
Next
From: "Huang, Suya"
Date:
Subject: huge pgstat.stat file on PostgreSQL 8.3.24