Re: A modest proposal: make parser/rewriter/planner inputs read-only - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: A modest proposal: make parser/rewriter/planner inputs read-only
Date
Msg-id 869744ec-4372-41c0-8fbd-4523f5d6dc93@gmail.com
Whole thread Raw
In response to A modest proposal: make parser/rewriter/planner inputs read-only  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: A modest proposal: make parser/rewriter/planner inputs read-only
List pgsql-hackers
On 4/5/25 18:46, Tom Lane wrote:
> I'm not planning to pursue this idea Right Now, but it seems like
> something that could happen for v19 or so.  In the meantime I wanted
> to get the ideas down on electrons.
> 
> Thoughts?
I generally like the idea because, for now, I need to be sure that no 
one touched the parse tree before copying it to do additional 
transformations before the optimisation phase.
But what is the way you are proposing here? Do you mean that one more 
entity will be explicitly introduced: a transformed parse tree?
It would open an opportunity for extensions to build a set of 
alternative transformed trees, pass them through the optimisation phase 
and choose the best plan.

-- 
regards, Andrei Lepikhov



pgsql-hackers by date:

Previous
From: Mahendra Singh Thalor
Date:
Subject: Re: [Proposal] Add \dAt [AMPTRN [TBLPTRN]] to list tables by Table Access Method in psql
Next
From: Andres Freund
Date:
Subject: Re: Recent pg_rewind test failures in buildfarm