| From: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: JIT compiling expressions/deform + inlining prototype v2.0 |
| Date: | 2017-09-05 10:58:56 |
| Message-ID: | 4e474a03-1b73-b8e0-725c-4d3e5c4f2bb6@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04.09.2017 23:52, Andres Freund wrote:
>
> Yea, I've changed that already, although it's currently added earlier,
> because the alignment is needed before, to access the column correctly.
> I've also made number of efficiency improvements, primarily to access
> columns with an absolute offset if all preceding ones are fixed width
> not null columns - that is quite noticeable performancewise.
Unfortunately, in most of real table columns are nullable.
I wonder if we can perform some optimization in this case (assuming that
in typical cases column either contains mostly non-null values, either
mostly null values).
--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2017-09-05 11:01:31 | Re: Partition-wise join for join between (declaratively) partitioned tables |
| Previous Message | Vladimir Borodin | 2017-09-05 10:54:13 | Re: Proposal: pg_rewind to skip config files |