Re: Building PG 8.2.3 for x86_64 on Mac OS X 10.4.9 - Mailing list pgsql-general

From Kevin Murphy
Subject Re: Building PG 8.2.3 for x86_64 on Mac OS X 10.4.9
Date
Msg-id 4628D8CA.1020204@genome.chop.edu
Whole thread Raw
In response to Re: Building PG 8.2.3 for x86_64 on Mac OS X 10.4.9  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Building PG 8.2.3 for x86_64 on Mac OS X 10.4.9  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane wrote:
> Kevin Murphy <murphy2@speakeasy.net> writes:
>
>> Has anybody tried making a 64-bit PostgreSQL on an Apple XServe w/
>> Intel Woodcrest CPU's?
>>
>> creating template1 database in /usr/local/src/postgresql-8.2.3/src/
>> test/regress/./tmp_check/data/base/1 ... FATAL:  \
>> could not create shared memory segment: Cannot allocate memory
>> DETAIL:  Failed system call was shmget(key=1, size=1810432, 03600).
>>
>
> Hmm ... not sure if this is related, but there's something mighty fishy
> about that "key" parameter.  I'd expect to see key=5432001, or something
> close to that depending on what port number you're using.
>
But is this the case when doing 'make check'?   I see this in postinit.c:

/*
 

                 * We're running a postgres bootstrap process or a
standalone backend.
                 * Create private "shmem" and
semaphores.

                 */
                CreateSharedMemoryAndSemaphores(true, 0);

where 0 is the port.

Since the ENOMEM problem occurs in a simple shared memory test program,
I'm inquiring on an Apple dev list.

-Kevin Murphy



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: cant get pg_dump/pg_restore to behave
Next
From: Tom Lane
Date:
Subject: Re: Building PG 8.2.3 for x86_64 on Mac OS X 10.4.9