On Wed, Nov 21, 2018 at 10:05:34AM -0500, Robert Haas wrote: > On Tue, Nov 20, 2018 at 1:21 AM Takahashi, Ryohei > <r.takahash...@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:"
> > 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. Windows ASLR can't explain your system's behavior. > You might be right, but maybe we should first try to understand why > this is happening so frequently. Maybe it's not that normal. When PostgreSQL installed that workaround, we weren't aware of any system where this message was common enough to make the log volume a problem. I agree the message is harmful on your system, but I'm not inclined to change it to DEBUG1 for the benefit of one system. Can you adopt pgbouncer, to reduce the frequency of starting new backend processes? That should improve your performance, too. Could you collect the information http://postgr.es/m/20181203053506.gb2860...@rfd.leadboat.com requests? That may help us understand your system's unusual behavior. (The issue in that thread is related but not identical.)
