Sv: Re: Early WIP/PoC for inlining CTEs

Andreas Joseph Krogh <andreas@visena.com>

From: Andreas Joseph Krogh <andreas@visena.com>

To: pgsql-hackers@lists.postgresql.org

Date: 2019-02-02T21:42:31Z

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

På lørdag 02. februar 2019 kl. 20:01:01, skrev Tom Lane <tgl@sss.pgh.pa.us 
<mailto:tgl@sss.pgh.pa.us>>: [snip]
 There's nothing particularly stopping us from accepting
 "materialized" with a D in this syntax, instead of or in addition
 to "materialize"; though I hesitate to mention it for fear of
 another round of bikeshedding.   +1 for keeping it "imperative-style" 
– MATERIALIZE – consistent with other SQL-stuff.   --
 Andreas Joseph Krogh