Re: Cygwin+Postgres+IpcMemoryCreate - Mailing list pgsql-cygwin

Bellan,

Please post instead of sending private email -- you will most likely get
a faster and better response.

I have never sent such problems with 7.2 and I can't imagine major
difference with 7.2.1.  I will try 7.2.1 soon but I can't give any ETA.

BTW, I did not see your post on pgsql-cygwin.  To which mailing list
were you referring?

Jason
Sincere apologies to send a direct mail to you. I was browsing through the
mailing lists for the problem I was facing and got your email address. I'm
quite desparate. I would appreciate if you just point me in the right
direction,
I've already posted this in the new groups.

Thank you so much.

I'm Running Postgres 7.2.1 on W2K box, Cygwin DLL 1.3.10 with 384M
Memory.
I'm pretty sure I have around 200M free memory when this error
occurs. If I look at the sequence of actions in the log,

1) FATAL 2: link from /cygdrive/C/pg/data/pg_xlog/0000000000000004 to
/cygdrive/C/pg/data/pg_xlog/0000000000000007 (initialization of log
file 0, segment 7) failed: Permission denied
2) One child process exits
3) SIGQUIT is sent to the other processes.
4) All the other children die
5) Reinitialize processes (all server processes terminated;
reinitializing shared memory and semaphores)
6) Then the error reads, IpcMemoryCreate: shmget(key=5432001,
size=1441792, 03600) failed: Not enough memory
Please help.
The actual log file section is below. FATAL 2:� link from
/cygdrive/C/pg/data/pg_xlog/0000000000000004 to
/cygdrive/C/pg/data/pg_xlog/0000000000000007 (initialization of log
file 0, segment 7) failed: Permission denied
..
..
..
..
...
..
DEBUG:� reaping dead processes
DEBUG:� child process (pid 488) exited with exit code 2
DEBUG:� server process (pid 488) exited with exit code 2
DEBUG:� terminating any other active server processes
DEBUG:� CleanupProc: sending SIGQUIT to process 320
DEBUG:� CleanupProc: sending SIGQUIT to process 2920
DEBUG:� CleanupProc: sending SIGQUIT to process 1996
DEBUG:� CleanupProc: sending SIGQUIT to process 2940
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:� StartTransactionCommand
DEBUG:� CommitTransactionCommand
DEBUG:� StartTransactionCommand
DEBUG:� CommitTransactionCommand
DEBUG:� StartTransactionCommand
DEBUG:� CommitTransactionCommand
DEBUG:� StartTransactionCommand
DEBUG:� CommitTransactionCommand
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.
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:� reaping dead processes
DEBUG:� child process (pid 320) exited with exit code 1
DEBUG:� reaping dead processes
DEBUG:� child process (pid 2920) exited with exit code 1
DEBUG:� child process (pid 1996) exited with exit code 1
DEBUG:� reaping dead processes
DEBUG:� reaping dead processes
DEBUG:� child process (pid 2940) exited with exit code 1
DEBUG:� all server processes terminated; reinitializing shared memory
and semaphores
IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not
enough memory 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.



_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com