Re: BUG #5264: could not create shared memory segment: Invalid argument

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: venkat nemani <nemani(dot)venkat87(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5264: could not create shared memory segment: Invalid argument
Date: 2010-01-05 10:26:41
Message-ID: 4B4313E1.8080207@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 5/01/2010 3:06 PM, venkat nemani wrote:

> 2010-01-05 12:30:00 IST HINT: This error usually means that PostgreSQL's
> request for a shared memory segment exceeded your kernel's SHMMAX parameter.
> You can either reduce the request size or reconfigure the kernel with
> larger SHMMAX. To reduce the request size (currently 1108156416 bytes),
> reduce PostgreSQL's shared_buffers parameter (currently 131072) and/or its
> max_connections parameter (currently 803).

This is not a bug. The hint above explains what is wrong, and the
PostgreSQL documentation goes into more detail on configuring shared memory.

You need to lower shared_buffers, lower max_connections, and/or increase
your kernel's shared memory limit.

With 803 connections, I'm guessing you have one connection per client.
Avoid this if possible - use a server-side connection pooler.

--
Craig Ringer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message AI Rumman 2010-01-05 12:23:19 BUG #5265: incomplete startup packet
Previous Message venkat nemani 2010-01-05 07:06:45 BUG #5264: could not create shared memory segment: Invalid argument