Re: BUG #5264: could not create shared memory segment: Invalid argument - Mailing list pgsql-bugs

From Craig Ringer
Subject Re: BUG #5264: could not create shared memory segment: Invalid argument
Date
Msg-id 4B4313E1.8080207@postnewspapers.com.au
Whole thread Raw
In response to BUG #5264: could not create shared memory segment: Invalid argument  ("venkat nemani" <nemani.venkat87@gmail.com>)
List 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

pgsql-bugs by date:

Previous
From: "venkat nemani"
Date:
Subject: BUG #5264: could not create shared memory segment: Invalid argument
Next
From: "AI Rumman"
Date:
Subject: BUG #5265: incomplete startup packet