Re: [bug fix] postgres.exe fails to start on Windows Server 2012 due to ASLR - Mailing list pgsql-hackers

From MauMau
Subject Re: [bug fix] postgres.exe fails to start on Windows Server 2012 due to ASLR
Date
Msg-id 0518EDB9561C4ED1936C1FC1EB8BF432@maumau
Whole thread Raw
In response to Re: [bug fix] postgres.exe fails to start on Windows Server 2012 due to ASLR  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: [bug fix] postgres.exe fails to start on Windows Server 2012 due to ASLR  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
From: "Craig Ringer" <craig@2ndquadrant.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




pgsql-hackers by date:

Previous
From: "MauMau"
Date:
Subject: Re: [bug fix] PostgreSQL fails to start on Windows if it crashes after tablespace creation
Next
From: Robert Haas
Date:
Subject: Re: inherit support for foreign tables