Re: Early WIP/PoC for inlining CTEs

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Early WIP/PoC for inlining CTEs
Date: 2019-01-22 03:47:36
Message-ID: 29ce1707-0dae-ad33-8ab0-7d5226c7dfd3@proxel.se
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On 1/10/19 2:28 AM, Andreas Karlsson wrote:
> Here is a new version of the patch with added tests, improved comments,
> some minor code cleanup and most importantly slightly changed logic for
> when we should inline.

Add ctematerialized to the JumbleExpr() in pg_stat_statements on
suggestion from Andrew Gierth. I think that is the correct thing to do
since it can have a major impact on performance.

Andreas

Attachment Content-Type Size
inlining-ctes-v8.patch text/x-patch 29.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hubert Zhang 2019-01-22 04:08:46 Re: Control your disk usage in PG: Introduction to Disk Quota Extension
Previous Message Chapman Flack 2019-01-22 03:26:43 Re: Allowing extensions to find out the OIDs of their member objects