From: | lst_hoe02(at)kwsoft(dot)de |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Postgres crash during low-traffic period, need advice. |
Date: | 2010-12-20 14:29:03 |
Message-ID: | 20101220152903.14587dtjezps3tgc@webmail.kwsoft.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Zitat von Benoit Clennett-Sirois <benoit(at)lesite(dot)ca>:
> Hi,
>
> 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.
Regards
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-12-20 14:34:06 | Re: Postgres crash during low-traffic period, need advice. |
Previous Message | Benoit Clennett-Sirois | 2010-12-20 13:41:53 | Postgres crash during low-traffic period, need advice. |