Re: initdb fails to allocate shared memory

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: initdb fails to allocate shared memory
Date: 2010-08-25 15:31:59
Message-ID: 1282750319.11634.119.camel@jd-desktop.unknown.charter.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Wed, 2010-08-25 at 11:15 -0400, A.M. wrote:
> I am using pgsql9.0b4 (but pgsql8.4 exhibits the same behavior) on MacOS 10.6.4 and initdb fails:
> initdb: removing data directory "/Volumes/Data/pgsql90b"
>
> I would like to create the database space and then reduce the shared memory requirements in postgresql.conf, but this situation seems to create a chicken-and-egg problem. How can I reduce shared_buffers or max_connections prior to running initdb?

If you don't have enough shared memory to initdb, you don't have enough
to run postgresql. You need to increase your shared memory for MacOS
per:

http://www.postgresql.org/docs/8.4/static/kernel-resources.html

And then initdb.

Sincerely,

Joshua D. Drake

--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thom Brown 2010-08-25 15:35:47 Re: unexpected message type 0x58 during COPY from stdin
Previous Message bricklen 2010-08-25 15:25:41 unexpected message type 0x58 during COPY from stdin

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Haggerty 2010-08-25 15:40:16 Re: git: uh-oh
Previous Message Markus Wanner 2010-08-25 15:30:07 Re: Deadlock bug