Re: Anything wrong with x86_64 and SYSV shared memory allocation?
Re: Anything wrong with x86_64 and SYSV shared memory allocation?
- Subject: Re: Anything wrong with x86_64 and SYSV shared memory allocation?
- From: Kevin Murphy <email@hidden>
- Date: Tue, 24 Apr 2007 11:00:32 -0400
On Apr 24, 2007, at 8:00 AM, Terry Lambert wrote:
On Apr 23, 2007, at 7:33 AM, Kevin Murphy wrote:
What I'm actually trying to do is compile 64-bit PostgreSQL, which
compiles fine using "-arch x86_64" in CFLAGS, but it fails its
regression tests because it can't allocate memory with shmget
(ENOMEM is returned). The 32-bit PostgreSQL compiles and works fine.
It's trying to allocate the memory in the lower 4G of the process
virtual address space, and unless you turn off the 4G page 0
mapping (or munamp() it after you're running but before you attempt
to allocate shared memory), it's not going to see any free address
space available.
Terry,
Thanks very much. I've forward the information to the PostgreSQL
community.
Since I'm not a hacker, my role at this point will be that of
interested bystander.
Regards,
Kevin Murphy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden