IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not enough memory

From: Murali Mohan Kasetty <kasetty(at)india(dot)hp(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not enough memory
Date: 2002-10-22 12:40:31
Message-ID: 3DB5473F.BF3517BE@india.hp.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,

I am using PostgreSQL version 7.2 in WIndows 2000. The postmaster
reports
the following problem and quits when lot of data is being inserted into
the
database.

Has anybody encountered a similar problem. If so, what is the solution
to
this. Are there any patches available for this error. Should we migrate
to a
different version.

We are going live this month end and it has become a show stopper now.

Thanks to all in advance for the response.

FATAL 2: link from /usr/local/pgsql/data/pg_xlog/0000000000000019 to
/usr/local
/pgsql/data/pg_xlog/000000000000001F (initialization of log file 0,
segment
31)
failed: Permission denied
DEBUG: server process (pid 2496) exited with exit code 2
DEBUG: terminating any other active server processes
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
DEBUG: all server processes terminated; reinitializing shared memory
and
semaph
ores
IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not
enough
mem
ory

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 1441792 bytes), reduce
PostgreSQL's shared_buffers parameter (currently 64) and/or
its max_connections parameter (currently 32).

The PostgreSQL Administrator's Guide contains more information about
shared memory configuration.

Best Regards
- Geetha
----------------------------------------------------
Hewlett Packard (India)
+91 80 2051382 (Phone)
847 1382 (HP Telnet)
----------------------------------------------------

Attachment Content-Type Size
kasetty.vcf text/x-vcard 339 bytes

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tommi Maekitalo 2002-10-22 12:45:01 Re: 7.1.3 : pg_dumpall does not work for me
Previous Message Andrei Ivanov 2002-10-22 12:30:46 problem with escaping "