Re: BUG #14050: "could not reserve shared memory region" in postgresql log

From: "Schuch, Mathias (Mathias)" <mschuch(at)avaya(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14050: "could not reserve shared memory region" in postgresql log
Date: 2016-04-06 09:07:05
Message-ID: C17BDE1BC28A314E927010993FFBA7F23A33A751@AZ-FFEXMB02.global.avaya.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I can't find the information how to enable this logging. Can tell me where to find this?

-----Ursprüngliche Nachricht-----
Von: Noah Misch [mailto:noah(at)leadboat(dot)com]
Gesendet: Mittwoch, 6. April 2016 08:08
An: Schuch, Mathias (Mathias) <mschuch(at)avaya(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Betreff: Re: BUG #14050: "could not reserve shared memory region" in postgresql log

On Mon, Apr 04, 2016 at 08:05:34AM +0000, Schuch, Mathias (Mathias) wrote:
> We use the PostgreSQL setup from EnterpriseDB. There is a McAfee VirisScan Enterprise 8.8 running on the system.

You could try updating to PostgreSQL 9.3.12 and disabling the antivirus software. I don't have a specific reason to expect those to help, but they're relatively easy.

In your position, I would next instrument postgres.exe to log a memory map of the child during pgwin32_ReserveSharedMemoryRegion(). That would show which DLL created the address space collision.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Suderevsky 2016-04-06 14:36:31 Re: PosgreSQL backend process crashed with signal 9
Previous Message yuan_rui1987 2016-04-06 06:10:38 BUG #14067: Wrong result of <select distinct geometry from XXX>