| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Jeremy Finzel <finzelj(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Early WIP/PoC for inlining CTEs |
| Date: | 2018-07-24 23:48:01 |
| Message-ID: | 87o9ewfbar.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Andres" == Andres Freund <andres(at)anarazel(dot)de> writes:
Andres> My read of the concensus (in which I am in the majority, so I
Andres> might be biased) is that we do want inlining to be the default.
Andres> We were thinking that it'd be necessary to provide a way to
Andres> force inlining on the SQL level for individual CTEs.
For the record, here is where it came up in the original discussion
exactly 10 years ago when the feature was being added:
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-07-24 23:49:19 | Re: Early WIP/PoC for inlining CTEs |
| Previous Message | Tomas Vondra | 2018-07-24 23:47:30 | pgsql: Add strict_multi_assignment and too_many_rows plpgsql checks |