From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andreas Karlsson <andreas(at)proxel(dot)se>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Early WIP/PoC for inlining CTEs |
Date: | 2018-11-16 22:41:07 |
Message-ID: | 20181116224107.GB958@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 16, 2018 at 04:15:10PM -0500, Tom Lane wrote:
> Andreas Karlsson <andreas(at)proxel(dot)se> writes:
> > [ inlining-ctes-v5.patch ]
>
> I took a little bit of a look through this. Some thoughts:
>
> * I think it'd be a good idea if we made OFFSET/LIMIT in a CTE be an
> alternate way of keeping it from being inlined. As the patch stands,
> if that's the behavior you want, you have no way to express it in
> a query that will also work in older servers. (I will manfully
> resist suggesting that then we don't need the nonstandard syntax
> at all ... oops, too late.)
If we're on board with exposing pilot error, we could decide not to
implement the nonstandard WITH syntax. One type of pilot error this
would expose is a situation where:
- A UDF has side effects, but is declared IMMUTABLE
- A WITH clause calls it in order to get those side effects on the
entire result set
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2018-11-16 23:04:38 | Re: Early WIP/PoC for inlining CTEs |
Previous Message | Thomas Munro | 2018-11-16 22:38:03 | Re: Refactoring the checkpointer's fsync request queue |