setting shmmax for postgres
mmiranda at 123.com.sv
Mon Mar 20 21:25:25 UTC 2006
Charles Swiger wrote:
> On Mar 20, 2006, at 3:36 PM, Miguel wrote:
>> shiva2# sysctl -a kern.ipc.shmmax
>> kern.ipc.shmmax: 2147483647
Opss, typo here, its 1147483647
>> but postgres always fails with this error
>> The PostgreSQL documentation contains more information about shared
>> memory configuration.
>> FATAL: could not create shared memory segment: Cannot allocate memory
>> DETAIL: Failed system call was shmget(key=5432001, size=1149067264,
>> HINT: This error usually means that PostgreSQL's request for a
>> shared memory segment exceeded available memory or swap space. To
>> reduce the request size (currently 1149067264 bytes), reduce
>> PostgreSQL's shared_buffers parameter (currently 137626) and/or its
>> max_connections parameter (currently 200).
> Just how much RAM do you have in the machine? I don't think you can
> allocate more than 256MB or so to SysV shared memory without tuning
> the number of KVA pages being allocated to the kernel...? Maybe it
> depends on whether the SysV shmem segments are wired down by default
> or not, I think there's a sysctl which controls that.
I have 3G of RAM
> You should revert Postgres back to a more reasonable default shared
> region size for now and rebuild the kernel to increase these
> parameters if you actually have the RAM and the need to do so.
I cant find any related in GENERIC
More information about the freebsd-questions