Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax - Mailing list pgsql-admin

From Pavan Deolasee
Subject Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax
Date
Msg-id CABOikdOyVvpJSk44iyA33bQVQMzZpn2bQ=NxTmZJ6r6F=62TMg@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax  (Mel Llaguno <mllaguno@coverity.com>)
Responses Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax  (Mel Llaguno <mllaguno@coverity.com>)
List pgsql-admin
On Thu, Feb 7, 2013 at 11:01 AM, Mel Llaguno <mllaguno@coverity.com> wrote:
> Having to guess this value is far from ideal; what I'd like is the formula used by postgresql that generates the
shmget()value displayed in the pgctl.log. 
>

There is no easy way or at least none that I'm aware of, to get the
exact value of shared memory needed for Postgres. If you have access
to the source code, you can look at CreateSharedMemoryAndSemaphores()
function in src/backend/storage/ipc/ipci.c to see what all goes in
determining the size for shmget()

Thanks,
Pavan

--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee


pgsql-admin by date:

Previous
From: Mel Llaguno
Date:
Subject: Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax
Next
From: Mel Llaguno
Date:
Subject: Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax