Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Mel Llaguno <mllaguno(at)coverity(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax
Date: 2013-02-07 05:41:46
Message-ID: CABOikdOyVvpJSk44iyA33bQVQMzZpn2bQ=NxTmZJ6r6F=62TMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Feb 7, 2013 at 11:01 AM, Mel Llaguno <mllaguno(at)coverity(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Mel Llaguno 2013-02-07 05:43:33 Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax
Previous Message Mel Llaguno 2013-02-07 05:31:18 Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax