Re: [HACKERS] JIT & function naming

2017-09-03 Thread Andres Freund
On 2017-09-03 10:11:37 -0400, Tom Lane wrote: > Andres Freund writes: > > Currently there's essentially a per EState counter and the generated > > functions get named deform$n and evalexpr$n. That allows for profiling > > of a single query, because different compiled

Re: [HACKERS] JIT & function naming

2017-09-03 Thread Tom Lane
Andres Freund writes: > Currently there's essentially a per EState counter and the generated > functions get named deform$n and evalexpr$n. That allows for profiling > of a single query, because different compiled expressions are > disambiguated. It even allows to run the same

Re: [HACKERS] JIT & function naming

2017-09-03 Thread Konstantin Knizhnik
On 09/03/2017 02:59 AM, Andres Freund wrote: Hi, On 2017-08-31 23:41:31 -0700, Andres Freund wrote: I previously had an early prototype of JITing [1] expression evaluation and tuple deforming. I've since then worked a lot on this. Here's an initial, not really pretty but functional,

Re: [HACKERS] JIT & function naming

2017-09-02 Thread Andres Freund
Hi, On 2017-08-31 23:41:31 -0700, Andres Freund wrote: > I previously had an early prototype of JITing [1] expression evaluation > and tuple deforming. I've since then worked a lot on this. > > Here's an initial, not really pretty but functional, submission. One of the things I'm not really