| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Magnus Hagander' <magnus(at)hagander(dot)net>, "Takahashi, Ryohei" <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-10 00:21:35 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1FB3C03B@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Magnus Hagander [mailto:magnus(at)hagander(dot)net]
> 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.
+1
We can change pgwin32_ReserveSharedMemoryRegion() to take an argument "int loglevel". Then the caller first calls it with LOG, and DEBUGx afterwards. It may also be helpful for the caller to output "LOG: tried %d times to reserve shared memory region" when the caller ran the function twice or more before success. That explains the possibly long time or CPU spikes of connection establishment.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tsunakawa, Takayuki | 2018-12-10 02:03:37 | RE: Statement-level rollback |
| Previous Message | Tom Lane | 2018-12-09 23:43:14 | Re: automatically assigning catalog toast oids |