From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Andreas Karlsson <andreas(at)proxel(dot)se> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Early WIP/PoC for inlining CTEs |
Date: | 2019-01-10 02:24:19 |
Message-ID: | CAEepm=2x3kJ5AdkKmEf_ODAZm7+e=7DW1u-+ZwfncWvd8xDaiA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 10, 2019 at 2:28 PM Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
> 2. Feedback on the new syntax. I am personally fine with the current
> syntax, but it was just something I just quickly hacked together to move
> the patch forward and which also solved my personal uses cases.
Thanks for working on this. I very much want to see this feature go
in. As mentioned by Andres up-thread, TPC-DS makes a lot of use of
CTEs... let me see, 34 queries out of 99 have a WITH clause. These
will hopefully become candidates for parallel query.
I know this is a thorny topic, but I have to say that I am uneasy
about the MATERIALIZED syntax. Here's how you write that in some
other RDBMS that loves hints:
WITH foo AS (SELECT /*+ MATERIALIZE */ ...)
I understood that it was a long standing project policy that we don't
want planner hints, but now we have a proposal to support one with a
top-level non-standard syntax. If we take this syntax, should we not
also accept MATERIALIZED in front of subselects?
-1
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Hugh Ranalli | 2019-01-10 02:52:05 | Re: BUG #15548: Unaccent does not remove combining diacritical characters |
Previous Message | Robert Haas | 2019-01-10 02:11:20 | Re: pgsql: Use perfect hashing, instead of binary search, for keyword looku |