From: | mariem <mariem(dot)benfadhel(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Convert query plan to sql query |
Date: | 2014-11-11 02:50:18 |
Message-ID: | 1415674218274-5826448.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>If what you're wishing for is that you could also capture the effects
>of planner steps that are in the nature of source-to-source
>transformations, I think that's going to be harder because no great
>effort has been made to keep those at arm's length from steps that
>don't have results describable as pure SQL. However, you could probably
>get pretty far if you applied ruleutils.c to the modified parse tree
>after the constant-folding and join tree simplification phases.
I'm not sure if I understand what you mean by source-to-source
transformations.
But yes, what I'm aiming is applying simplification phases and
constant-folding before transforming the query tree back to sql text query.
Thank you for the suggestions.
Best,
Mariem
--
View this message in context: http://postgresql.nabble.com/Convert-query-plan-to-sql-query-tp5825727p5826448.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2014-11-11 03:35:22 | Re: using custom scan nodes to prototype parallel sequential scan |
Previous Message | Alvaro Herrera | 2014-11-11 02:14:02 | Re: BRIN indexes - TRAP: BadArgument |