Robert Haas writes:
> On Wed, Jul 31, 2013 at 4:35 PM, Robert Lerche (rlerche)
> wrote:
>> Hi. Has anyone had experience building PostgreSQL to support Address Space
>> Layout Randomization (ASLR)? I recently took a brute-force approach
>> (compiling everything with -fPIC and specifying -pie on
On 2013-08-04 21:07:02 -0400, Robert Haas wrote:
> On Sun, Aug 4, 2013 at 8:54 PM, Andres Freund wrote:
> >> AFAIK you've got it backwards: ASLR is something that happens
> >> automatically, unless you take steps to suppress it, at least on MacOS
> >> X. I not long ago built with EXEC_BACKEND on
On Sun, Aug 4, 2013 at 8:54 PM, Andres Freund wrote:
>> AFAIK you've got it backwards: ASLR is something that happens
>> automatically, unless you take steps to suppress it, at least on MacOS
>> X. I not long ago built with EXEC_BACKEND on that platform and found
>> that it broke stuff until I di
On 2013-08-04 20:33:50 -0400, Robert Haas wrote:
> On Wed, Jul 31, 2013 at 4:35 PM, Robert Lerche (rlerche)
> wrote:
> > Hi. Has anyone had experience building PostgreSQL to support Address Space
> > Layout Randomization (ASLR)? I recently took a brute-force approach
> > (compiling everything wi
On Wed, Jul 31, 2013 at 4:35 PM, Robert Lerche (rlerche)
wrote:
> Hi. Has anyone had experience building PostgreSQL to support Address Space
> Layout Randomization (ASLR)? I recently took a brute-force approach
> (compiling everything with -fPIC and specifying -pie on all executables).
> This wo
Hi. Has anyone had experience building PostgreSQL to support Address Space
Layout Randomization (ASLR)? I recently took a brute-force approach (compiling
everything with -fPIC and specifying -pie on all executables). This worked,
but a (very superficial) performance test indicated a high cost
