Too many logs are written on Windows (LOG: could not reserveshared memory region (addr=%p) for child %p:) - Mailing list pgsql-hackers

From Takahashi, Ryohei
Subject Too many logs are written on Windows (LOG: could not reserveshared memory region (addr=%p) for child %p:)
Date
Msg-id EE586BE92A4AFB45B03310C2A0C0565D6D0FE960@G01JPEXMBKW03
Whole thread Raw
Responses Re: Too many logs are written on Windows (LOG: could not reserveshared memory region (addr=%p) for child %p:)
List pgsql-hackers
Hi,


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.
Ifso, I think administrators are not interested in this log since it is a normal event. 
 

I think the log level should not be "LOG", but should be lower level such as "DEBUG1".


Regards,
Ryohei Takahashi




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query
Next
From: Amit Langote
Date:
Subject: Re: typo fix