Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax
От | Mel Llaguno |
---|---|
Тема | Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax |
Дата | |
Msg-id | E1FB7FBAE29E634FA58D6CC0D59F288B11EF73D7@CH1PRD0511MB442.namprd05.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax (Pavan Deolasee <pavan.deolasee@gmail.com>) |
Список | pgsql-admin |
Pavan, Thanks. I'll have a look at the source code. M. ________________________________________ From: Pavan Deolasee [pavan.deolasee@gmail.com] Sent: Wednesday, February 06, 2013 10:41 PM To: Mel Llaguno Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] PostgreSQL's share_buffer calculation using shmget() versus kernel.shmmax 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 по дате отправления: