Re: Improving executor performance - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Improving executor performance
Date
Msg-id 20160714210959.nangfbqxby5pkyjg@alap3.anarazel.de
Whole thread Raw
In response to Re: Improving executor performance  (Andreas Seltenreich <seltenreich@gmx.de>)
Responses Re: Improving executor performance  (Andreas Seltenreich <seltenreich@gmx.de>)
List pgsql-hackers
On 2016-07-14 23:03:10 +0200, Andreas Seltenreich wrote:
> That's the plan, yes.  I'm sorry there's no publishable code yet on the
> the postgres side of things.  Using libFirm[1], the plan is to.

Why libfirm? It seems to only have x86 and sparc backends, and no
windows support?


> 1. Automatically generate Firm-IR for the static C code around
>    expression evaluation as well operators in the system catalog.

> 2. Construct IR for expression trees (essentially all the function calls
>    the executor would do).

But that essentially means redoing most of execQual's current code in IR
- or do you want to do that via 1) above?  As long as the preparation
code (which is currently intermixed with the execution phase) isn't
separated, that means pulling essentially the whole backend given that
we do catalog lookups and everything during that phase.


> Currently, a student at credativ is working on applying these
> techniques to postgres.

Are you planning to support this to postgres proper?


Regards,

Andres



pgsql-hackers by date:

Previous
From: Andreas Seltenreich
Date:
Subject: Re: Improving executor performance
Next
From: Greg Stark
Date:
Subject: Re: sslmode=require fallback