Postgres Pro
Downloads
Home   >   mailing lists

Thread: Problems Starting Postgres as a Service

Problems Starting Postgres as a Service

From
Nick Stone
Date:
Hi

I am trying to run Postgres on Windows as a service and after a bit of
playing around I can run it from within Cygwin and I can install it as a
service OK but when I try to start the service I get the following error:

> IpcMemoryCreate: shmget(key=5432001, size=1499136, 03600) failed: Not
enough core
>
> 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 1499136 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.

I have followed all the various how-to's / faq notes etc. and I realise that
the error message has some clues as to a possible solution but could someone
explain why I can start Postgres from the command prompt but not as a
service? Also what are the effects of reducing some of the parameters
mentioned in the error message?

Many thanks

Nick

Re: Problems Starting Postgres as a Service

From
"Ian Huynh"
Date:
while postgres is pretty solid under unixes,
i am just curious as regards to the stability of cygwin+Postgres combo under win2k?

-----Original Message-----
From: Nick Stone [mailto:nick.stone@digitalvision.com]
Sent: Wednesday, September 03, 2003 1:57 AM
To: 'pgsql-admin@postgresql.org'
Subject: [ADMIN] Problems Starting Postgres as a Service


Hi

I am trying to run Postgres on Windows as a service and after a bit of
playing around I can run it from within Cygwin and I can install it as a
service OK but when I try to start the service I get the following error:

> IpcMemoryCreate: shmget(key=5432001, size=1499136, 03600) failed: Not
enough core
>
> 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 1499136 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.

I have followed all the various how-to's / faq notes etc. and I realise that
the error message has some clues as to a possible solution but could someone
explain why I can start Postgres from the command prompt but not as a
service? Also what are the effects of reducing some of the parameters
mentioned in the error message?

Many thanks

Nick

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org

Re: Problems Starting Postgres as a Service

From
Al Hulaton
Date:
On Wed, 2003-09-03 at 15:21, Ian Huynh wrote:
> while postgres is pretty solid under unixes,
> i am just curious as regards to the stability of cygwin+Postgres combo under win2k?

Since Cygwin is an emulation layer running on Windows, performance of
PostgreSQL + Cygwin isn't comparable to a pure *nix environment.

For instance, above 50 concurrent connections, Cygwin starts getting
unstable which is why we hard code a conneciton limit in our Windows
version of Mammoth PosgreSQL. For this reason, PostgreSQL + Cygwin is
typically used in development or low-load environments.

It's still usuable, just not as scalable as a pure linux/unix solution.

--
Best,
Al Hulaton    |  Sr. Account Engineer  |  Command Prompt, Inc.
503.222.2783  |  ahulaton@commandprompt.com
Home of Mammoth PostgreSQL and 'Practical PostgreSQL'
Managed PostgreSQL, Linux services and consulting
Read and Search O'Reilly's 'Practical PostgreSQL' at
http://www.commandprompt.com