Re: Too many logs are written on Windows (LOG: could not reserve shared memory region (addr=%p) for child %p:)

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: r(dot)takahashi_2(at)jp(dot)fujitsu(dot)com
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Too many logs are written on Windows (LOG: could not reserve shared memory region (addr=%p) for child %p:)
Date: 2018-12-07 09:33:04
Message-ID: CABUevEx9eRSKvgF6_fgOuewUVRP_u8TdbDAg1cpQKACNLNsgwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 6, 2018 at 7:04 AM Takahashi, Ryohei <
r(dot)takahashi_2(at)jp(dot)fujitsu(dot)com> wrote:

> Hi,
>
>
> I found the reason of the message.
>
> My customer uses "F-secure" antivirus software.
> There are several pages that indicate F-secure causes this message such as
> [1].
> I told my customer to stop F-secure and report to the vendor.
>
>
> Anyway, I think this message is not helpful to administrators and should
> be lower level such as "DEBUG1".
>
>
In this particular case, it seems it *was* helpful, no? That's how you
found out the customer used a broken antivirus product, which may certainly
also cause *other* issues.

Some sort of rate limiting to reduce the volume might help, but the message
itself seems to have clearly been useful.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message PG Bug reporting form 2018-12-07 10:42:54 BUG #15541: Use after release in PQprint
Previous Message Andrey Borodin 2018-12-07 09:14:31 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock