On 3 March 2014 13:27, Sorin Sbârnea <email address hidden> wrote:
> I have the same problem with latest LTS Ubuntu, and the proper solution
> is to set BOTH SHMMAX and SHMALL to the same value, the best is ¼ of
> total memory.
>
> kernel.shmmax = xxx
> kernel.shmall = xxx
>
> Still, I would consider this an real bug, especially because the
> postgres error is misleading and incomplete.
SHMALL is measured in pages, whereas SHMMAX is measured in bytes. They
shouldn't be set to the same values as one another.
On 3 March 2014 13:27, Sorin Sbârnea <email address hidden> wrote:
> I have the same problem with latest LTS Ubuntu, and the proper solution
> is to set BOTH SHMMAX and SHMALL to the same value, the best is ¼ of
> total memory.
>
> kernel.shmmax = xxx
> kernel.shmall = xxx
>
> Still, I would consider this an real bug, especially because the
> postgres error is misleading and incomplete.
SHMALL is measured in pages, whereas SHMMAX is measured in bytes. They
shouldn't be set to the same values as one another.
Regards
Thom