Re: A note about testing EXEC_BACKEND on recent Linuxen

From: Mitchell Skinner <mitch(at)arctur(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: A note about testing EXEC_BACKEND on recent Linuxen
Date: 2006-01-27 15:00:21
Message-ID: 1138374021.16221.18.camel@firebolt
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2006-01-26 at 18:40 -0500, Tom Lane wrote:
> You can work around this by doing (as root)
> echo 0 >/proc/sys/kernel/randomize_va_space
> before starting the postmaster. You'll probably want to set it back to
> 1 when done experimenting with EXEC_BACKEND, since address randomization
> is a useful security hack.

I haven't fiddled with this myself, but according to Arjan van de Ven's
post to fedora-devel on July 30th 2005,
> setarch has an -R option to start the binary without randomisation.

...so that you can turn it off per-execution rather than system-wide.
I'm not sure if children inherit the setting.

Mitch

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-01-27 15:09:00 Re: Adding a --quiet option to initdb
Previous Message Tom Lane 2006-01-27 14:26:48 stats for failed transactions (was Re: [GENERAL] VACUUM Question)