On 05/14/2012 12:10 PM, Matthijs Kooijman wrote:
hi,
> Sorry for the useless noise.
Easy to be confused about this paramaters.
> Ah, right. In that case, perhaps postgresql somehow allocates different
> amounts of SHM based on some autodetection mechanism or other
> circumstance, and lxc is so
Hi Papp,
> >> kernel.shmmni = 4096
> > I assume you misspelled "shmmin" there?
>
> No.
> Do you have shmmin?:)
Oh, never mind me. I had assumed the SHMMIN mentioned in the postgresql
output would have a sysctl:
> If the request size is already small, it's possible that it is less
> than your ke
On 05/14/2012 11:05 AM, Matthijs Kooijman wrote:
hi!
>> kernel.shmmax = 2147483648
>> kernel.shmall = 2147483648
>> kernel.shmmni = 4096
> I assume you misspelled "shmmin" there?
No.
Do you have shmmin?:)
> Where did you set these values?
sysctl -a|grep shm
>> Originally the maximum value was
Hi Papp,
> kernel.shmmax = 2147483648
> kernel.shmall = 2147483648
> kernel.shmmni = 4096
I assume you misspelled "shmmin" there?
Where did you set these values?
> Originally the maximum value was 25M, I don't know how, but I could
> increase it until 29M.
> It starts fine with shared_buffers
hi!
I want to increase shared_buffers value.
Machine has 8GB of RAM.
OS is Ubuntu Precise on both host and container.
kernel.shmmax = 2147483648
kernel.shmall = 2147483648
kernel.shmmni = 4096
Originally the maximum value was 25M, I don't know how, but I could
increase it until 29M.
It starts
