On Wed, Sep 4, 2019 at 11:24 AM Andres Freund <and...@anarazel.de> wrote:
> Hi, > > On 2019-09-04 07:51:16 -0700, Andres Freund wrote: > > Or better, something slightly more complete, like the attached (which > affects both code-gen time optimizations (which are more like peephole > ones), and both function/global ones that are cheap). > Yes, that does completely solve the issue I raised. It makes JIT either better or at least harmless, even when falling into the gap between jit_above_cost and jit_optimize_above_cost. What TPC-H implementation do you use/recommend? This one https://wiki.postgresql.org/wiki/DBT-3? Cheers, Jeff
