From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Self-modifying code |
Date: | 2005-12-16 22:00:48 |
Message-ID: | 20051216220048.GA28739@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > I just read an article on LWN.net about the usage of self-modifying code
> > for selecting the optimum code for a given operation at run time.
>
> That went out with hula hoops, I think. For sure the security
> implications of making your code segment writable mean that the bar for
> "is it worth it" is a WHOLE lot higher than "it might possibly make TAS
> a bit faster".
Actually I was thinking in the issue with defining different sets of TAS
for SMP versus non-SMP. There was discussion that suggested handing off
two set of binaries, one for each configuration. So it's not just "it
might possibly" but rather a possible answer to that problem, which was
not mentioned as minor and for which a solution was not found AFAIR.
However it's not something that I'll personally code, so I'll let
somebody else argue about it if they really care about the issue. I
just felt the need to mention it.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2005-12-16 22:36:14 | second "begin transaction" emits a warning |
Previous Message | Pierre Girard | 2005-12-16 21:35:57 | Re: Solaris cc compiler on amd: PostgreSQL does not have native |