From: | Adam Witney <awitney(at)sghms(dot)ac(dot)uk> |
---|---|
To: | John DeSoi <jd(at)icx(dot)net> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: shared memory on OS X - 7.4beta4 |
Date: | 2003-10-27 00:07:52 |
Message-ID: | BBC21258.27090%awitney@sghms.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 26/10/03 9:41 pm, "John DeSoi" <jd(at)icx(dot)net> wrote:
> Adam,
>
> On Sunday, October 26, 2003, at 10:16 AM, Adam Witney wrote:
>
>> Ah, yes I did change these... Mine are set to
>>
>> sysctl -w kern.sysv.shmmax=4194304
>> sysctl -w kern.sysv.shmmin=1
>> sysctl -w kern.sysv.shmmni=32
>> sysctl -w kern.sysv.shmseg=8
>> sysctl -w kern.sysv.shmall=1024
>
>
> OK, this is what I was after. I did not have to change any of this for
> 7.3, but now 7.4 does not work unless on a standard OS X installation
> unless the user modifies these system settings. I can live with it, but
> I was hoping it might be a bug that could be resolved before the final
> 7.4. Every person that installs on OS X is going to run into this.
> Tracking it down and understanding what you have to change is not
> simple for us OS X users that are not familiar with Unix :).
Well I had to change this for 7.3 to run and I never set it back to try 7.4
with the defaults
But I think the 7.4 installation process checks for the best values of
max_connections and shared_buffers that for the current settings shmmax
settings
But someone else on the list is probably better to answer the technical
details of this
adam
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Kohll | 2003-10-27 00:13:06 | Re: Retrieving a column comment |
Previous Message | Alvaro Herrera | 2003-10-26 23:03:18 | Re: Retrieving a column comment |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2003-10-27 00:09:19 | Re: Still a few flaws in configure's default CFLAGS selection |
Previous Message | Gaetano Mendola | 2003-10-26 23:35:52 | Autocomplete <TAB> on Postgres7.4beta5 not working? |