Thanks John, but someone have just fixed the problem. I still need to find
out about the fix.
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of John R Pierce
Sent: Wednesday, April 24, 2013 8:18 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] FATAL: shmat(id=3342337) failed: Cannot allocate
memory
On 4/23/2013 11:08 PM, Khangelani Gama wrote:
> Hi John
>
> Yes that's the whole messege
>
well, try something like...
kernel.shmmax = 4294967295
kernel.shmall = 268435456
at the end of /etc/sysctl.conf, then execute `sysctl -p` and try to start
postgres again.
(it really doesn't matter if you set those kernel limits too large, they
have no negative impact, they are simply quota, the max allowed. The
only reason to restrict them is on a shared system with hostile/malicious
users like students who might mess with grabbing excessive memory and
causing a denial of service. )
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
CONFIDENTIALITY NOTICE
The contents of and attachments to this e-mail are intended for the addressee only, and may contain the confidential
information of Argility (Proprietary) Limited and/or its subsidiaries. Any review, use or dissemination thereof by
anyone
other than the intended addressee is prohibited.If you are not the intended addressee please notify the writer
immediately
and destroy the e-mail. Argility (Proprietary) Limited and its subsidiaries distance themselves from and accept no
liability
for unauthorised use of their e-mail facilities or e-mails sent other than strictly for business purposes.