Re: BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log.

Force ASLR is not enabled for PostgreSQL.

I made further investigations. If I delay PostgreSQL start (by using "Delayed Start" -option with PostgreSQL -service or by starting manually PostgreSQL) the problem disappears.
So trigger for the problems might be high CPU of high hard-disk load on windows startup -phase. Or some dependency to other windows service.
---
Jari

-----Original Message-----
From: Michael Paquier [mailto:michael(dot)paquier(at)gmail(dot)com]
Sent: 12. marraskuuta 2016 6:58
To: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>
Cc: Jari Kopponen <jari(dot)kopponen(at)patria(dot)fi>; PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log.

On Fri, Nov 11, 2016 at 11:22 PM, Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com> wrote:
> FWIW, there was 3 reports for this issue on french board in the last
> few days (including pg 9.3.3 and 9.5.5), I think all of them on W7.

It may be a good idea to check if ASLR is really enabled. Win2k8 R2 and Win7 SP1 have introduced the "force ASLR" feature...
https://support.microsoft.com/en-us/kb/2639308
Not sure if that's related directly to that, but the reports popping up with the latest versions of Win7 and win2k8 are pointing out to something that the OS changed...
--
Michael