Re: Unable to allocate 2G of shared memory on wheezy

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Cramer <davecramer(at)gmail(dot)com>
Cc: pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Unable to allocate 2G of shared memory on wheezy
Date: 2014-06-18 19:37:27
Message-ID: 27332.1403120247@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Dave Cramer <davecramer(at)gmail(dot)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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Huang, Suya 2014-06-19 04:38:54 huge pgstat.stat file on PostgreSQL 8.3.24
Previous Message Dave Cramer 2014-06-18 19:33:58 Re: Unable to allocate 2G of shared memory on wheezy