@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
a
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 matte
:8184 kB
DirectMap2M: 905216 kB
-Original Message-
From: Khangelani Gama [mailto:kg...@argility.com]
Sent: Wednesday, April 24, 2013 8:09 AM
To: 'John R Pierce'; 'pgsql-general@postgresql.org'
Subject: RE: [GENERAL] FATAL: shmat(id=3342337) failed: Cannot
hanks
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Wednesday, April 24, 2013 7:58 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] FATAL: shmat(id=3342337) failed: Cannot allocate
memory
On 4/23
On 4/23/2013 10:53 PM, Khangelani Gama wrote:
We are running postgres 9.1 on CentOS 5. We can’t start up postgres .
It complains about memory allocation . Please help
FATAL: shmat(id=3342337) failed: Cannot allocate memory
is that the entire error message? it usually says something about
Hi all
We are running postgres 9.1 on CentOS 5. We can’t start up postgres . It
complains about memory allocation . Please help
FATAL: shmat(id=3342337) failed: Cannot allocate memory
# - Memory -
shared_buffers = 310251
# (change requires r
