| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, 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-17 15:48:07 |
| Message-ID: | 00818be9-2f63-f584-efcd-d97ee0662905@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/11/19 8:10 PM, Robert Haas wrote:
> WITH cte_name [[NOT] MATERIALIZED] AS (query) main_query...
Hm, when would one want "NOT MATERIALIZED"? I am not sure I see the
usefulness of forcing inlining other than if we by default do not inline
when a CTE is referenced multiple times.
Do you imaging it working something like the below?
1. Default
# Not inlined
- Referenced multiple times
- Includes FOR UPDATE|SHARE
- Includes volatile functions
- Recurisve
- DML
# Inlined
- Simple case (no side effects, referenced once)
2. MATERIALIZED
# Not inlined
- Everything
# Inlined
- (none)
3. NOT MATERIALIZED
# Not inlined
- Recursive
- DML
# Inlined
- Everything else
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Karlsson | 2019-01-17 15:52:04 | Re: Feature: temporary materialized views |
| Previous Message | Tom Lane | 2019-01-17 15:23:39 | Re: ArchiveEntry optional arguments refactoring |