I get this when I try to start up a freshly compiled beta4 on OS X
10.2.6:
FATAL: could not create shared memory segment: Invalid argument
I saw a previous thread on this for beta2. It sounded like this was a
bug that was to be fixed in beta3, but I'm still having this problem
with beta4.
Th
On Friday, October 24, 2003, at 10:19 AM, Adam Witney wrote:
I don't know what this error is particularly, but just to say that
7.4beta5
compiles and starts up fine on my OSX 10.2.8 machine
OK, I compiled beta 5 and put my rest SHMMAX back to the default
settings as provided by OS X. Still the s
>> And here are are the default settings for OS X 10.2.6:
>>
>> sysctl -w kern.sysv.shmmax=4194304
>
>Well, I can only say that if I lower shmmax to that value, initdb picks
>max_connections = 50
>shared_buffers = 300
I just did a fresh install of 7.4b5 on a fresh install of MacOS 10.3, and i
Slightly off topic confirmations...
And here are are the default settings for OS X 10.2.6:
sysctl -w kern.sysv.shmmax=4194304
Seems to be the default on 10.2.8 as well.
10.1.5 doesn't seem to have a kern.sysv.* section:
[broccoli:~] erics% sysctl kern.sysv.shmmax
second level name sysv in k
John DeSoi <[EMAIL PROTECTED]> writes:
> What version of OS X are you running? I thought I replicated the
> problem after upgrading to 10.2.8, but now I'm not certain I ran initdb
> again (I may have just rebuilt beta 5). So possibly it could be a
> difference between 10.2.6 and 10.2.8. If not,
