Re: [HACKERS] CTE inlining - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] CTE inlining
Date
Msg-id 20170430052816.n2j52g4za37emp2f@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] CTE inlining  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2017-04-30 00:28:46 -0400, Tom Lane wrote:
> There's already a pretty large hill to climb here in the way of
> breaking peoples' expectations about CTEs being optimization
> fences.  Breaking the documented semantics about CTEs being
> single-evaluation seems to me to be an absolute non-starter.

If all referenced functions are non-volatile, I don't quite see the
problem?  Personally I believe we'll have to offer a proper
anti-inlining workaround anyway, and in that case there's really nothing
that should stop us from inlining CTE without volatile functions twice?

- Andres



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] CTE inlining
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] CTE inlining