Postgres Pro
Downloads
Home   >   mailing lists

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

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

ipcs -m

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status



Dave Cramer


On 18 June 2014 15:15, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Dave Cramer <davecramer@gmail.com> writes:
> To reduce the request size [FAILently 2232950784 bytes), reduce
> PostgreSQL's shared memory usage,

This error message is a bit garbled :-(.  It would've been useful
to know the specific errno, but you've trimmed out that info.

Perhaps it's failing because you already have ~10G in shared memory
segments?  "sudo ipcs -m" might be illuminating.

                        regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Unable to allocate 2G of shared memory on wheezy
Next
From: Dave Cramer
Date:
Subject: Re: Unable to allocate 2G of shared memory on wheezy