Thread: Accessing PostgreSQL Database Crashes Server

Accessing PostgreSQL Database Crashes Server

From
bradjwilkins@netscape.net
Date:
I have the exact same problem that Alexei Tenitski has.

I have no problems initializing and starting the PostgreSQL database server (using postmaster or as an Windows
service).

However, as soon as I attempt to use the database (using make checkinstall or psql), the server crashes/stops and
outputsthe following error: 

>>>>>

ZeroProcSemaphore: semctl(id=0,SETVAL) failed: Invalid argument
DEBUG:  server process (pid 1108) exited with exit code 255
DEBUG:  terminating any other active server processes
DEBUG:  all server processes terminated; reinitializing shared memory and semaph
ores
IpcMemoryCreate: shmget(key=5432001, size=655360, 03600) failed: Not enough memo
ry

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

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

<<<<<

I have played with shared_buffers and max_connections with no luck.

Has anyone figure out what the problem is?  All help is sincerely appreciated.

Thanks,
Brad Wilkins


__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with
Shop@Netscape!http://shopnow.netscape.com/ 

Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/