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

From: "Takahashi, Ryohei" <r(dot)takahashi_2(at)jp(dot)fujitsu(dot)com>
To: 'Michael Paquier' <michael(at)paquier(dot)xyz>
Cc: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, 'Magnus Hagander' <magnus(at)hagander(dot)net>, 'Noah Misch' <noah(at)leadboat(dot)com>, 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-10 08:13:21
Message-ID: EE586BE92A4AFB45B03310C2A0C0565D6D33EAFD@G01JPEXMBKW03
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Thank you for replying.

> Like a couple of others on this thread I doubt that lowering the elevel
> here would be a good thing, as keeping it noisy has been what allows to
> know that something has gone wrong, no? The current behavior is
> useful.

Currently, I agree with you.
I cancel my proposal.

Regards,
Ryohei Takahashi

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message amul sul 2018-12-10 09:06:23 Re: vacuum and autovacuum - is it good to configure the threshold at TABLE LEVEL?
Previous Message Michael Paquier 2018-12-10 06:33:07 Re: [PATCH] Log PostgreSQL version number on startup