Re: Early WIP/PoC for inlining CTEs
David Fetter <david@fetter.org>
From: David Fetter <david@fetter.org>
To: Andreas Karlsson <andreas@proxel.se>
Cc: Andrew Gierth <andrew@tao11.riddles.org.uk>, Nico Williams <nico@cryptonector.com>, pgsql-hackers@postgresql.org
Date: 2018-07-26T14:46:55Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Prevent inlining of multiply-referenced CTEs with outer recursive refs.
- 9476131278c7 12.0 landed
-
Allow user control of CTE materialization, and change the default behavior.
- 608b167f9f9c 12.0 landed
-
Split QTW_EXAMINE_RTES flag into QTW_EXAMINE_RTES_BEFORE/_AFTER.
- 18c0da88a5d9 12.0 landed
-
document when PREPARE uses generic plans
- fab9d1da4a21 9.6.0 cited
On Thu, Jul 26, 2018 at 02:51:53PM +0200, Andreas Karlsson wrote: > On 07/25/2018 06:08 PM, Andrew Gierth wrote: > >WITH ctename AS [[NOT] MATERIALIZED] (query) > > I think "NOT MATERIALIZED" would be a bit misleading since the > planner may choose to materialize anyway, so I suggest skipping that > part of the syntax unless there is a really strong reason for having > it. If we're going to give people specific knobs to turn as part of queries to affect query plans[1], we should think it through at a much higher level than this. If we're not going to do that right away, we just need to treat instances where the wrong call was made as planner bugs and address them at that level. Best, David. [1] Not to use the word that starts with 'h' and sounds like lints http://pghintplan.osdn.jp/ -- 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