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-04 08:05:34
Message-ID: C17BDE1BC28A314E927010993FFBA7F23A33555A@AZ-FFEXMB02.global.avaya.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

We use the PostgreSQL setup from EnterpriseDB. There is a McAfee VirisScan Enterprise 8.8 running on the system.

-----Ursprüngliche Nachricht-----
Von: Noah Misch [mailto:noah(at)leadboat(dot)com]
Gesendet: Sonntag, 3. April 2016 22:58
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 Tue, Mar 29, 2016 at 09:38:04AM +0000, mschuch(at)avaya(dot)com wrote:
> PostgreSQL version: 9.3.5
> Operating system: Windows 7

> 2016-03-16 14:45:28 EST LOG: could not reserve shared memory region
> (addr=0000000001BB0000) for child 000000000000047C: error code 487
> 2016-03-16 14:45:28 EST LOG: could not fork autovacuum worker
> process: A blocking operation was interrupted by a call to WSACancelBlockingCall.
>
> I read in the release notes that this issue should be solved with
> 9.3.4 but with 9.3.5 it isn't.

We had not seen this on Windows 7. From where did you download the PostgreSQL binaries, or with which tools did you build them? Which antivirus and/or anti-malware software does this system use?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2016-04-04 16:08:01 Re: BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled
Previous Message Michael Paquier 2016-04-04 06:22:22 Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby