| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux? |
| Date: | 2021-08-12 15:13:17 |
| Message-ID: | 4082215.1628781197@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Aug 11, 2021 at 6:24 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jordan Gigov | 2021-08-12 15:23:41 | Expanding regexp_matches flags |
| Previous Message | Robert Haas | 2021-08-12 15:00:23 | Re: Next Steps with Hash Indexes |