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

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Craig Ringer" <craig(at)2ndquadrant(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 11:28:14
Message-ID: 0518EDB9561C4ED1936C1FC1EB8BF432@maumau
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: "Craig Ringer" <craig(at)2ndquadrant(dot)com>
> 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.

Please don't mind, I didn't misunderstand your intent. I think we should
apply this in the next minor release to avoid unnecessary confusion -- more
new users would use PostgreSQL on Windows 8/2012 and hit this problem.

I added this patch to the CommitFest.

Regards
MauMau

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-02-04 11:56:00 Re: inherit support for foreign tables
Previous Message MauMau 2014-02-04 10:47:49 Re: [bug fix] PostgreSQL fails to start on Windows if it crashes after tablespace creation