| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Colin Watson <cjwatson(at)canonical(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Backport "WITH ... AS MATERIALIZED" syntax to <12? |
| Date: | 2019-11-05 00:20:20 |
| Message-ID: | CA+hUKGJL+CWc5Mw+FB3GTczOT3oZ8D1O9CA7uuB1codr+qZgkg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Oct 19, 2019 at 11:52 PM Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> I wonder if an extension could do something like that, though. It can
> install a hook after parse analysis, so I guess it could walk the CTEs
> and mark them as materialized.
I wonder if the existing pg_hint_plan extension could be extended to
do that using something like /*+ MATERIALIZE */. That'd presumably be
ignored when not installed/not understood etc. I've never used
pg_hint_plan myself and don't know how or how well it works, but it
look like it supports Oracle-style hints hidden in comments like /*+
HashJoin(a b) */ rather than SQL Server-style hints that are in the
SQL grammar itself like SELECT ... FROM a HASH JOIN b.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-11-05 00:22:20 | Re: [PATCH] Do not use StdRdOptions in Access Methods |
| Previous Message | Noah Misch | 2019-11-04 23:43:09 | Re: SimpleLruTruncate() mutual exclusion |