Re: [bug fix] postgres.exe fails to start on Windows Server 2012 due to ASLR

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: MauMau <maumau307(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [bug fix] postgres.exe fails to start on Windows Server 2012 due to ASLR
Date: 2014-02-04 02:33:03
Message-ID: 52F0515F.4010101@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/01/2014 09:53 PM, MauMau wrote:
>
> Not all users use PostgreSQL built by EnterpriseDB, so I think
> src\tools\msvc\build.bat should produce modules that are not affected by
> ASLR.

I completely agree; just saying that any installer can set the key.

I'm convinced that setting this flag is appropriate, at least while Pg
relies on having the shared memory segment mapped in the same zone in
every executable. Just pointing out that there's a workaround in the
mean time.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2014-02-04 03:23:29 Re: Prohibit row-security + inheritance in 9.4?
Previous Message Michael Paquier 2014-02-04 02:18:01 Re: Regression tests failing if not launched on db "regression"