Re: Too many logs are written on Windows (LOG: could not reserveshared memory region (addr=%p) for child %p:)
От | Robert Haas |
---|---|
Тема | Re: Too many logs are written on Windows (LOG: could not reserveshared memory region (addr=%p) for child %p:) |
Дата | |
Msg-id | CA+Tgmoa0w6rA+=tfm_JeOyU1DRduksK1ThMi6r=R2uCbizQcEA@mail.gmail.com обсуждение исходный текст |
Ответ на | Too many logs are written on Windows (LOG: could not reserveshared memory region (addr=%p) for child %p:) ("Takahashi, Ryohei" <r.takahashi_2@jp.fujitsu.com>) |
Ответы |
RE: Too many logs are written on Windows (LOG: could not reserveshared memory region (addr=%p) for child %p:)
Re: Too many logs are written on Windows (LOG: could not reserveshared memory region (addr=%p) for child %p:) |
Список | pgsql-hackers |
On Tue, Nov 20, 2018 at 1:21 AM Takahashi, Ryohei <r.takahashi_2@jp.fujitsu.com> wrote: > My customer uses PostgreSQL on Windows and hits the problem that following log is written to the server logs too frequently(250 thousand times per day). > "LOG: could not reserve shared memory region (addr=%p) for child %p:" > > This log is written when pgwin32_ReserveSharedMemoryRegion() in win32_shmem.c fails. If fails, internal_forkexec() in postmaster.cretries up to 100 times. In most of my customer cases, internal_forkexec() finally succeeded to pgwin32_ReserveSharedMemoryRegion()by retrying. > > According to the comment of internal_forkexec(), pgwin32_ReserveSharedMemoryRegion() sometimes fails if ASLR is active.If so, I think administrators are not interested in this log since it is a normal event. You might be right, but maybe we should first try to understand why this is happening so frequently. Maybe it's not that normal. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: