Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux?
Date
Msg-id 4082215.1628781197@sss.pgh.pa.us
Whole thread Raw
In response to Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux?  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Aug 11, 2021 at 6:24 PM Thomas Munro <thomas.munro@gmail.com> wrote:
>> ... I think just doing
>> something like (/me rolls dice) export PG_SHMEM_ADDR=0x80000000000 is
>> a good candidate for something that works on both architectures, being
>> many TB away from everything else (above everything on ARM, between
>> heap etc and libs on Intel but with 8TB of space below it and 120TB
>> above).  That gets the tests passing consistently with unpatched
>> master, -DEXEC_BACKEND, on both flavours of silicon.

> Ugh, OK. So, is there a way that we can get an "easy button" committed
> to the tree?

I don't see why that approach couldn't be incorporated into pg_ctl,
or the postmaster itself.  Given Andres' point that Linux ASLR
disable probably has to happen in pg_ctl, it seems like doing it
in pg_ctl in all cases is the way to move forward.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Next Steps with Hash Indexes
Next
From: Jordan Gigov
Date:
Subject: Expanding regexp_matches flags