Postgres Pro
Downloads
Home   >   mailing lists

FATAL: shmat(id=3342337) failed: Cannot allocate memory - Mailing list pgsql-general

From Khangelani Gama
Subject FATAL: shmat(id=3342337) failed: Cannot allocate memory
Date
Msg-id bdce38bc27f6a81eb5b2d48581b71764@mail.gmail.com
Whole thread Raw
Responses Re: FATAL: shmat(id=3342337) failed: Cannot allocate memory
List pgsql-general
Tree view

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 restart)

#temp_buffers = 8MB                     # min 800kB

#max_prepared_transactions = 0          # zero disables the feature

                                        # (change requires restart)

# Note:  Increasing max_prepared_transactions costs ~600 bytes of shared memory

# per transaction slot, plus lock space (see max_locks_per_transaction).

# It is not advisable to set max_prepared_transactions nonzero unless you

# actively intend to use prepared transactions.

work_mem = 32MB                         # min 64kB

maintenance_work_mem = 512MB            # min 1MB

#max_stack_depth = 2MB                  # min 100kB

 

 

 

 

/etc/sysctl.conf

 

# Controls the default maxmimum size of a mesage queue

kernel.msgmax = 65536

 

# Controls the maximum shared segment size, in bytes

kernel.shmmax = 4294967295

 

# Controls the maximum number of shared memory segments, in pages

kernel.shmall = 26843545

 

 

 

 

 

------ Shared Memory Segments --------

key        shmid      owner      perms      bytes      nattch     status

0x7a014a02 32768      zabbix    666        971500     6

 

------ Semaphore Arrays --------

key        semid      owner      perms      nsems

0x7a014a02 0          zabbix    666        3

 

------ Message Queues --------

key        msqid      owner      perms      used-bytes   messages

 

 

 

Thanks

 

 

 


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.

pgsql-general by date:

Previous
From: Konstantin Izmailov
Date:
Subject: Re: inserting into "date" field returns error (COPY/BINARY)
Next
From: John R Pierce
Date:
Subject: Re: FATAL: shmat(id=3342337) failed: Cannot allocate memory