On Mon, Dec 20, 2010 at 9:29 AM, <lst_hoe02(at)kwsoft(dot)de> wrote:
> Zitat von Benoit Clennett-Sirois <benoit(at)lesite(dot)ca>:
>> We have a front-end server taking care of Nginx, memcached and
>> Postgresql. Last night the postgres daemon crashed (traffic was very
>> low at that time) with the following error:
>> 2010-12-20 03:34:30 EST DETAIL: Failed system call was
>> shmget(key=5432001, size=1124474880, 03600).
>> 2010-12-20 03:34:30 EST 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 1124474880
>> bytes), reduce PostgreSQL's shared_buffers parameter (currently
>> 131072) and/or its max_connections parameter (currently 963).
> For me this looks like you have shared_buffers at the default value of 128kb
> eg. 131072 Byte which would be way to low for 963 connections...
> Not sure if this is a reason to crash.
Actually I think that they mean that I have 131072 buffers * (BLCKSZ
value set at compile time) bytes each.. or something like that.. no?
It seems that in the documentation, in PG 8.1 you specified the number
of buffers and in PG 8.4 (the version i'm using) you specify the
amount of memory for shared buffers.
In response to
pgsql-admin by date
|Next:||From: Lou Picciano||Date: 2010-12-20 16:06:22|
|Subject: Is any 'upgrade' required to move a 9.0.1 cluster to 9.0.2?|
|Previous:||From: Scott Marlowe||Date: 2010-12-20 14:34:06|
|Subject: Re: Postgres crash during low-traffic period, need advice.|